openharmony/third_party_rust_lazy-static.rs
1
0
Fork 0
mirror of https://gitee.com/openharmony/third_party_rust_lazy-static.rs synced 2024-12-02 12:57:03 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Added notes on compile tests

Browse Source
This commit is contained in:
Łukasz Neumann 2017-11-12 03:01:17 +01:00
parent 6529b0739d
commit e5b681587f
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
tests/compile-fail/README.md Normal file
View File

@ -0,0 +1,22 @@
This directory contains snippets of code that should yield a
warning/note/help/error at compilation. Syntax of annotations is described in
[rust documentation](https://github.com/rust-lang/rust/blob/master/src/test/COMPILER_TESTS.md).
For more information check out [`compiletest` crate](https://github.com/laumann/compiletest-rs).
To run compile tests issue `cargo +nightly --test --features compiletest`.
## Notes on working with `compiletest` crate
* Currently code that is inside macro should not be annotated, as `compiletest`
crate cannot deal with the fact that macro invocations effectively changes
line numbering. To prevent this add a `// error-pattern:<your error message here>`
on the top of the file and make sure that you set `deny` lint level
if you want to test compiler message different than error.
* `compiletest` crate by default sets `allow(dead_code)` lint level so make sure
that you change it to something suiting your needs even if the warning is
issued prior to any macro invocation.
* If you get a message `error: 0 unexpected errors found, 1 expected errors not found`
despite the fact that some error was bound to occur don't worry - it's a known
issue in the `compiletest` crate and your error was probably not registered -
make sure that your annotations are correct and that you are setting correct
lint levels.