| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-05-05 | Update tests | Guillaume Gomez | -2/+2 | |
| 2020-03-26 | introduce `negative_impls` feature gate and document | Niko Matsakis | -1/+1 | |
| 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. | ||||
| 2018-12-27 | Simplify foreign type rendering. | John Heitmann | -4/+4 | |
| Simplified foreign type rendering by switching from tables to flexbox. Also, removed some seemingly extraneous elements like “ghost” spans. Reduces element count on std::iter::Iterator by 30%. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -11/+0 | |
| 2018-10-25 | Check for negative impls when finding auto traits | Aaron Hill | -0/+27 | |
| 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). | ||||
