about summary refs log tree commit diff
path: root/src/test/run-pass/extoption_env-not-defined.rs
AgeCommit message (Collapse)AuthorLines
2019-07-27tests: Move run-pass tests without naming conflicts to uiVadim Petrochenkov-5/+0
2019-07-27tests: Add missing run-pass annotationsVadim Petrochenkov-0/+2
2018-12-25Remove licensesMark Rousskov-11/+0
2015-04-08Remove pretty-expanded from failing testsAlex Crichton-1/+0
This commit removes pretty-expanded from all tests that wind up calling panic! one way or another now that its internals are unstable.
2015-03-23rustdoc: Replace no-pretty-expanded with pretty-expandedBrian Anderson-0/+2
Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work.
2013-09-25Fix run-pass tests to have 'pub fn main'Alex Crichton-1/+1
This is required by the check-fast target because each test is slurped up into a submodule.
2013-08-11Fixed option_env! typeSteven Fackler-2/+1
The type of the result of option_env! was not fully specified in the None case, leading to type check failures in the case where the variable was not defined (e.g. option_env!("FOO").is_none()).
2013-08-08env! syntax extension changesSteven Fackler-0/+14
env! aborts compilation of the specified environment variable is not defined and takes an optional second argument containing a custom error message. option_env! creates an Option<&'static str> containing the value of the environment variable. There are no run-pass tests that check the behavior when the environment variable is defined since the test framework doesn't support setting environment variables at compile time as opposed to runtime. However, both env! and option_env! are used inside of rustc itself, which should act as a sufficient test. Close #2248