| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-12-18 | Check FnPtr/FnDef built-in fn traits correctly with effects | Michael Goulet | -1/+1 | |
| 2023-12-16 | Remove unnecessary constness from ProjectionCandidate | Michael Goulet | -4/+2 | |
| 2023-12-08 | Implement `async gen` blocks | Michael Goulet | -2/+6 | |
| 2023-12-06 | EvaluatedToUnknown -> EvaluatedToAmbigStackDependent, EvaluatedToRecur -> ↵ | Michael Goulet | -10/+10 | |
| EvaluatedToErrStackDependent | ||||
| 2023-10-27 | Make `gen` blocks implement the `Iterator` trait | Oli Scherer | -0/+4 | |
| 2023-10-20 | s/generator/coroutine/ | Oli Scherer | -2/+2 | |
| 2023-10-20 | s/Generator/Coroutine/ | Oli Scherer | -2/+2 | |
| 2023-09-18 | Remove more unused `Lift` impls. | Nicholas Nethercote | -1/+1 | |
| 2023-08-14 | Remove constness from `ImplSource::Param` | Deadbeef | -0/+1 | |
| 2023-07-25 | Make everything builtin! | Michael Goulet | -3/+1 | |
| 2023-04-26 | Remove unused `TypeFoldable`/`TypeVisitable` impls. | Nicholas Nethercote | -1/+1 | |
| 2023-01-12 | attempt to make a minimal example work | Deadbeef | -1/+3 | |
| 2022-11-25 | add comment | lcnr | -0/+6 | |
| 2022-11-25 | move 2 candidates into builtin candidate | lcnr | -6/+0 | |
| 2022-11-24 | Avoid `GenFuture` shim when compiling async constructs | Arpad Borsos | -0/+4 | |
| Previously, async constructs would be lowered to "normal" generators, with an additional `from_generator` / `GenFuture` shim in between to convert from `Generator` to `Future`. The compiler will now special-case these generators internally so that async constructs will *directly* implement `Future` without the need to go through the `from_generator` / `GenFuture` shim. The primary motivation for this change was hiding this implementation detail in stack traces and debuginfo, but it can in theory also help the optimizer as there is less abstractions to see through. | ||||
| 2022-10-10 | Rollup merge of #102786 - compiler-errors:no-tuple-candidate, r=lcnr | Dylan DPC | -3/+0 | |
| Remove tuple candidate, nothing special about it r? `@lcnr` you mentioned this during the talk you gave i think | ||||
| 2022-10-07 | Remove tuple candidate, nothing special about it | Michael Goulet | -3/+0 | |
| 2022-10-07 | Remove `DefId` from some `SelectionCandidate` variants | Deadbeef | -2/+2 | |
| 2022-09-18 | make projection bounds with const bounds satisfy const | Deadbeef | -2/+3 | |
| 2022-08-07 | Built-in implementation of Tuple trait | Michael Goulet | -0/+3 | |
| 2022-07-27 | Initial (incomplete) implementation of transmutability trait. | Jack Wrenn | -0/+4 | |
| This initial implementation handles transmutations between types with specified layouts, except when references are involved. Co-authored-by: Igor null <m1el.2027@gmail.com> | ||||
| 2022-07-08 | Auto merge of #98614 - oli-obk:take_unsound_opaque_types, r=wesleywiser | bors | -4/+14 | |
| don't succeed `evaluate_obligation` query if new opaque types were registered fixes #98608 fixes #98604 The root cause of all this is that in type flag computation we entirely ignore nongeneric things like struct fields and the signature of function items. So if a flag had to be set for a struct if it is set for a field, that will only happen if the field is generic, as only the generic parameters are checked. I now believe we cannot use type flags to handle opaque types. They seem like the wrong tool for this. Instead, this PR replaces the previous logic by adding a new variant of `EvaluatedToOk`: `EvaluatedToOkModuloOpaqueTypes`, which says that there were some opaque types that got hidden types bound, but that binding may not have been legal (because we don't know if the opaque type was in its defining scope or not). | ||||
| 2022-07-07 | not knowing about opaque types is worse than not knowing about regions, make ↵ | Oli Scherer | -2/+2 | |
| sure we don't accidentally mark something as ok-modulo-regions if there are opaque types involved | ||||
| 2022-07-05 | impl TypeVisitable in type traversal macros | Alan Egerton | -1/+1 | |
| 2022-07-05 | Add #[derive(TypeVisitable)] | Alan Egerton | -1/+1 | |
| 2022-06-30 | Make `evaluate_obligation` not succeed unconditionally if it registered new ↵ | Oli Scherer | -4/+14 | |
| hidden types for opaque types | ||||
| 2022-03-26 | Do not use ParamEnv::and to cache param-env with candidate | Michael Goulet | -3/+10 | |
| 2022-03-25 | Fix ice when error reporting recursion errors | lightning1141 | -1/+14 | |
| Fixes: #90319, #92148, #93955 | ||||
| 2022-03-21 | Rename `~const Drop` to `~const Destruct` | Deadbeef | -2/+2 | |
| 2022-01-18 | Check const Drop impls considering ConstIfConst bounds | Michael Goulet | -2/+2 | |
| 2021-12-12 | Revert "Auto merge of #91491 - spastorino:revert-91354, r=oli-obk" | Deadbeef | -6/+4 | |
| This reverts commit ff2439b7b9bafcfdff86b7847128014699df8442, reversing changes made to 2a9e0831d6603d87220cedd1b1293e2eb82ef55c. | ||||
| 2021-12-03 | Revert "Auto merge of #91354 - fee1-dead:const_env, r=spastorino" | Santiago Pastorino | -4/+6 | |
| This reverts commit 18bb8c61a975fff6424cda831ace5b0404277145, reversing changes made to d9baa361902b172be716f96619b909f340802dea. | ||||
| 2021-11-29 | Avoid storing the ImplPolarity and Constness next to a TraitRef and use ↵ | Oli Scherer | -1/+1 | |
| TraitPredicate instead | ||||
| 2021-11-29 | Replace `ConstnessAnd<TraitRef>` with `TraitPredicate` which conveys the ↵ | Oli Scherer | -4/+2 | |
| same information | ||||
| 2021-11-29 | Prefer TraitPredicate over ConstnessAnd<TraitRef> | Oli Scherer | -1/+1 | |
| 2021-10-20 | Make EvaluationCache consider polarity as cache's key | Santiago Pastorino | -2/+4 | |
| 2021-10-20 | Consider negative polarity on overlap check | Santiago Pastorino | -2/+2 | |
| 2021-10-10 | Fix spelling: Cannonical -> Canonical | John Kugelman | -2/+2 | |
| 2021-10-05 | Issue 89275 fix and test | Tom Farmer | -4/+10 | |
| Issue 89275 fix and test Fix librustdoc OverflowError usage rust tidy run Issue 89275 fix and test | ||||
| 2021-09-15 | Coerce const FnDefs to implement const Fn traits | Deadbeef | -1/+3 | |
| 2021-09-09 | Const drop selection candidates | Deadbeef | -0/+3 | |
| 2021-08-22 | Fix typos “a”→“an” | Frank Steffahn | -1/+1 | |
| 2021-08-18 | Properly generate multiple candidates for trait upcasting coercion. | Charles Lew | -0/+5 | |
| 2021-08-13 | Make selection and evaluation caches use constness | Deadbeef | -2/+2 | |
| 2021-02-15 | Add `ptr::Pointee` trait (for all types) and `ptr::metadata` function | Simon Sapin | -0/+3 | |
| RFC: https://github.com/rust-lang/rfcs/pull/2580 | ||||
| 2020-11-22 | Thread `Constness` through selection | Jonas Schievink | -1/+1 | |
| 2020-10-22 | Normalize when finding trait object candidates | Matthew Jasper | -1/+4 | |
| 2020-10-06 | Handle multiple applicable projection candidates | Matthew Jasper | -3/+4 | |
| 2020-08-30 | mv compiler to compiler/ | mark | -0/+255 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |