| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-08-30 | mv compiler to compiler/ | mark | -40/+0 | |
| 2020-08-24 | Stabilize Range[Inclusive]::is_empty | Scott McMurray | -1/+0 | |
| I would like to propose these two simple methods for stabilization: - Knowing that a range is exhaused isn't otherwise trivial - Clippy would like to suggest them, but had to do extra work to disable that path <https://github.com/rust-lang/rust-clippy/issues/3807> because they're unstable - These work on `PartialOrd`, consistently with now-stable `contains`, and are thus more general than iterator-based approaches that need `Step` - They've been unchanged for some time, and have picked up uses in the compiler - Stabilizing them doesn't block any future iterator-based is_empty plans, as the inherent ones are preferred in name resolution | ||||
| 2020-08-15 | replaced log with tracing | Gurpreet Singh | -1/+1 | |
| 2020-07-22 | Increase accuracy of lifetime bound on trait object impl suggestion | Esteban Küber | -0/+1 | |
| 2020-07-16 | apply bootstrap cfgs | Mark Rousskov | -1/+0 | |
| 2020-06-28 | Remove `const_if_match` feature gate from libraries | Dylan MacKenzie | -1/+1 | |
| 2020-06-22 | rewrite leak check to be based on universes | Niko Matsakis | -0/+3 | |
| In the new leak check, instead of getting a list of placeholders to track, we look for any placeholder that is part of a universe which was created during the snapshot. We are looking for the following error patterns: * P1: P2, where P1 != P2 * P1: R, where R is in some universe that cannot name P1 This new leak check is more precise than before, in that it accepts this patterns: * R: P1, even if R cannot name P1, because R = 'static is a valid sol'n * R: P1, R: P2, as above Note that this leak check, when running during subtyping, is less efficient than before in some sense because it is going to check and re-check all the universes created since the snapshot. We're going to move when the leak check runs to try and correct that. | ||||
| 2020-05-29 | Add Extend::{extend_one,extend_reserve} | Josh Stone | -0/+1 | |
| This adds new optional methods on `Extend`: `extend_one` add a single element to the collection, and `extend_reserve` pre-allocates space for the predicted number of incoming elements. These are used in `Iterator` for `partition` and `unzip` as they shuffle elements one-at-a-time into their respective collections. | ||||
| 2020-04-19 | Dogfood more or_patterns in the compiler | Josh Stone | -0/+1 | |
| 2020-03-30 | rustc -> rustc_middle part 1 | Mazdak Farrokhzad | -1/+1 | |
| 2020-03-14 | Trim dependencies and features. | Camille GILLOT | -4/+2 | |
| 2020-03-10 | rust-lang.github.io/rustc-dev-guide -> rustc-dev-guide.rust-lang.org | Santiago Pastorino | -1/+1 | |
| 2020-03-10 | Rename rustc guide to rustc dev guide | Santiago Pastorino | -2/+2 | |
| 2020-03-10 | Rename rustc-guide to rustc-dev-guide | Santiago Pastorino | -1/+1 | |
| 2020-02-16 | Gate macro use. | Camille GILLOT | -0/+1 | |
| 2020-02-16 | Prune features. | Camille GILLOT | -23/+0 | |
| 2020-02-16 | Remove librustc_infer crate re-exports. | Camille GILLOT | -7/+0 | |
| 2020-02-16 | Make librustc_infer compile. | Camille GILLOT | -0/+67 | |
