| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-12-19 | docs: Fix outdated crate reference | pierwill | -1/+1 | |
| 2020-11-14 | Introduce `TypeVisitor::BreakTy` | LeSeulArtichaut | -0/+1 | |
| 2020-11-04 | Split the "raw integer bytes" part out of `Scalar` | Oliver Scherer | -0/+1 | |
| 2020-10-30 | TypeVisitor: use `std::ops::ControlFlow` instead of `bool` | LeSeulArtichaut | -0/+1 | |
| 2020-10-28 | Dogfood {exclusive,half-open} ranges in compiler (nfc) | Jubilee Young | -0/+2 | |
| In particular, this allows us to write more explicit matches that avoid the pitfalls of using a fully general fall-through case, yet remain fairly ergonomic. Less logic is in guard cases, more is in the actual exhaustive case analysis. No functional changes. | ||||
| 2020-09-23 | /nightly/nightly-rustc | Erik Hofmayer | -1/+1 | |
| 2020-09-23 | Updated html_root_url for compiler crates | Erik Hofmayer | -1/+1 | |
| 2020-09-20 | Rollup merge of #76825 - lcnr:array-windows-apply, r=varkor | Ralf Jung | -0/+1 | |
| use `array_windows` instead of `windows` in the compiler I do think these changes are beautiful, but do have to admit that using type inference for the window length can easily be confusing. This seems like a general issue with const generics, where inferring constants adds an additional complexity which users have to learn and keep in mind. | ||||
| 2020-09-20 | use `array_windows` instead of `windows` in the compiler | Bastian Kauschke | -0/+1 | |
| 2020-09-17 | Remove redundant #![feature(...)] 's from compiler/ | est31 | -5/+0 | |
| 2020-08-30 | datastructures: replace `once_cell` crate with an impl from std | marmeladema | -0/+1 | |
| 2020-08-30 | mv compiler to compiler/ | mark | -0/+93 | |
