mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4ed8cfc202
rust/tests/rustdoc/issue-55321.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

19 lines
731 B
Rust
Raw Normal View History

introduce `negative_impls` feature gate and document They used to be covered by `optin_builtin_traits` but negative impls are now applicable to all traits, not just auto traits. This also adds docs in the unstable book for the current state of auto traits.
2020-01-09 04:56:38 -06:00
#![feature(negative_impls)]
Check for negative impls when finding auto traits Fixes #55321 When AutoTraitFinder begins examining a type, it checks for an explicit negative impl. However, it wasn't checking for negative impls found when calling 'select' on predicates found from nested obligations. This commit makes AutoTraitFinder check for negative impls whenever it makes a call to 'select'. If a negative impl is found, it immediately bails out. Normal users of SelectioContext don't need to worry about this, since they stop as soon as an Unimplemented error is encountered. However, we add predicates to our ParamEnv when we encounter this error, so we need to handle negative impls specially (so that we don't try adding them to our ParamEnv).
2018-10-25 14:14:32 -05:00
// @has issue_55321/struct.A.html
rustdoc: update test cases now that code-header is used without in-band
2022-09-25 15:52:26 -05:00
// @has - '//*[@id="trait-implementations-list"]//*[@class="impl has-srclink"]//h3[@class="code-header"]' \
Update rustdoc tests
2021-06-02 03:59:10 -05:00
// "impl !Send for A"
rustdoc: update test cases now that code-header is used without in-band
2022-09-25 15:52:26 -05:00
// @has - '//*[@id="trait-implementations-list"]//*[@class="impl has-srclink"]//h3[@class="code-header"]' \
Update rustdoc tests
2021-06-02 03:59:10 -05:00
// "impl !Sync for A"
Check for negative impls when finding auto traits Fixes #55321 When AutoTraitFinder begins examining a type, it checks for an explicit negative impl. However, it wasn't checking for negative impls found when calling 'select' on predicates found from nested obligations. This commit makes AutoTraitFinder check for negative impls whenever it makes a call to 'select'. If a negative impl is found, it immediately bails out. Normal users of SelectioContext don't need to worry about this, since they stop as soon as an Unimplemented error is encountered. However, we add predicates to our ParamEnv when we encounter this error, so we need to handle negative impls specially (so that we don't try adding them to our ParamEnv).
2018-10-25 14:14:32 -05:00
pub struct A();
impl !Send for A {}
impl !Sync for A {}
// @has issue_55321/struct.B.html
rustdoc: update test cases now that code-header is used without in-band
2022-09-25 15:52:26 -05:00
// @has - '//*[@id="synthetic-implementations-list"]//*[@class="impl has-srclink"]//h3[@class="code-header"]' \
Update rustdoc tests
2021-06-02 03:59:10 -05:00
// "impl<T> !Send for B<T>"
rustdoc: update test cases now that code-header is used without in-band
2022-09-25 15:52:26 -05:00
// @has - '//*[@id="synthetic-implementations-list"]//*[@class="impl has-srclink"]//h3[@class="code-header"]' \
Update rustdoc tests
2021-06-02 03:59:10 -05:00
// "impl<T> !Sync for B<T>"
Check for negative impls when finding auto traits Fixes #55321 When AutoTraitFinder begins examining a type, it checks for an explicit negative impl. However, it wasn't checking for negative impls found when calling 'select' on predicates found from nested obligations. This commit makes AutoTraitFinder check for negative impls whenever it makes a call to 'select'. If a negative impl is found, it immediately bails out. Normal users of SelectioContext don't need to worry about this, since they stop as soon as an Unimplemented error is encountered. However, we add predicates to our ParamEnv when we encounter this error, so we need to handle negative impls specially (so that we don't try adding them to our ParamEnv).
2018-10-25 14:14:32 -05:00
pub struct B<T: ?Sized>(A, Box<T>);
Reference in New Issue Copy Permalink