Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use std in Windows test runner #6330

Closed
huonw opened this issue May 8, 2013 · 3 comments
Closed

use std in Windows test runner #6330

huonw opened this issue May 8, 2013 · 3 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc

Comments

@huonw
Copy link
Member

huonw commented May 8, 2013

As seen in #6267, when running the tests on Windows there are slightly different things in scope than when the tests are run normally. per @nikomatsakis:

The problem is that the checkfast procedure does not generate a use std at the top of the combined program that it generates. This is not really a concern of this PR in particular, but it'd be simple enough to fix. I am inclined to think, as a separate issue, that use std ought to be in the prelude. In any case, rather than JUST xfail-fasting them, can we put a comment as well explaining why? Potentially we could open an issue for this problem as well.

@emberian
Copy link
Member

see also #4193

@pnkfelix
Copy link
Member

Part of #8844.

@alexcrichton
Copy link
Member

Closing, #13288 removed check-fast

flip1995 pushed a commit to flip1995/rust that referenced this issue Dec 20, 2020
Add Redundant else lint

changelog: Add redundant_else lint

It seemed appropriate for "pedantic".

Closes rust-lang#112 \*blows off dust*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Development

No branches or pull requests

4 participants