-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Allow multiple imports and exports per statement #817
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
Labels
A-frontend
Area: Compiler frontend (errors, parsing and HIR)
Comments
brson
added a commit
that referenced
this issue
Aug 17, 2011
brson
added a commit
that referenced
this issue
Aug 17, 2011
Like so: import foo::{bar, baz}; Issue #817
brson
added a commit
that referenced
this issue
Aug 17, 2011
brson
added a commit
that referenced
this issue
Aug 17, 2011
brson
added a commit
that referenced
this issue
Aug 17, 2011
brson
added a commit
that referenced
this issue
Aug 17, 2011
Multiple import syntax is |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
May 5, 2022
`redundant_closure` fix FP on coerced closure Closes rust-lang/rust-clippy#8416, Closes rust-lang/rust-clippy#7812 Closes rust-lang/rust-clippy#8091 ~~Seems like this is fixed in rust-lang#817 and regressed.~~ Ignore coerced closure false positives, but this will lead to some false negatives on resolvable generics. IMO, this is still an overall improvement changelog: [`redundant_closure`] ignores coerced closure
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
These changes set all temporary variables as hidden. The cbmc trace will no longer include them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example, allow something like "export foo, bar, baz;" and "import foo, bar, baz from quux;"
I don't really care about the syntax.
The text was updated successfully, but these errors were encountered: