auto: Fix unused imports by alexcrichton · Pull Request #4803 · rust-lang/rust

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton · 2013-02-05T17:42:31Z

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the unused_imports warning/deny attribute.

Before this patch there were these problems:

Unused imports from prelude.rs were warned about with dummy spans, leading to a large number of confusing warnings.
Unused imports from intrinsic.rs were warned about with the file <intrinsic> which couldn't be forced to go away
Methods used from imported traites (like io::WriterUtil) resulted in an unused warning of the import even though it was used.
If one use statement imported N modules, M of which weren't used, M warning statements were issued.
If a glob import statement was used, each public export of the target module which wasn't used had a warning issued.

This patch deals with all these cases by doing:

Ignore unused imports from prelude.rs (indicated by a dummy span of 0)
Ignore unused imports from intrinsic.rs (test on the imported module name, is there a better way?)
Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing.
Only issue one warning statement
Only issue one warning statement.

This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

1. Don't warn about anything not used in the prelude which is autmoatically injected, accomplished with a test that the span is equal to a dummy span. 2. Don't warn about unused imports from the injected intrinsic module, accomplished by testing against the name of the imported module 3. If anything is used from a glob import, don't warn about the glob import. 4. If an import imports more than one thing, and none of them are used, only issue a warning once Also updated the unused-imports-warn test to have stricter requirements on error messages.

The first commit message has most of the comments, but this pull request basically fixes a lot of issues surrounding the `unused_imports` warning/deny attribute. Before this patch there were these problems: 1. Unused imports from `prelude.rs` were warned about with dummy spans, leading to a large number of confusing warnings. 2. Unused imports from `intrinsic.rs` were warned about with the file `<intrinsic>` which couldn't be forced to go away 3. Methods used from imported traites (like `io::WriterUtil`) resulted in an unused warning of the import even though it was used. 4. If one `use` statement imported N modules, M of which weren't used, M warning statements were issued. 5. If a glob import statement was used, each public export of the target module which wasn't used had a warning issued. This patch deals with all these cases by doing: 1. Ignore unused imports from `prelude.rs` (indicated by a dummy span of 0) 2. Ignore unused imports from `intrinsic.rs` (test on the imported module name, is there a better way?) 3. Track when imported modules are used as candidates for methods, and just assume they're used. This may not end up being the actual case, but in theory not warning about an unused thing is worse than warning about a used thing. 4. Only issue one warning statement 5. Only issue one warning statement. This is the first time I've edited the compiler itself, and I tried to keep up with the style around, but I may have missed something here or there...

add check_only feature for faster check builds

4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

alexcrichton added 2 commits February 5, 2013 12:40

Don't warn when imported traits are indeed used
b368cb2

bors closed this Feb 8, 2013

alexcrichton mentioned this pull request Feb 8, 2013
Unused import check doesn't consider impls #1630
Closed

RalfJung added a commit to RalfJung/rust that referenced this pull request Jan 4, 2026
Merge pull requestrust-lang#4803from RalfJung/check_only
dbf2ef7
add check_only feature for faster check builds

github-actionsBot mentioned this pull request Jan 27, 2026
Toolchain upgrade to nightly-2026-02-09 flux-rs/flux#1345
Closed

U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
Mergerust-lang#4803
6f0cc91
4803: Parse default unsafe fn r=matklad a=Avi-D-coder Co-authored-by: Avi Dessauer <avi.the.coder@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

alexcrichton commented Feb 5, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!