| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-12-24 | x.py fmt after previous deignore | Mark Rousskov | -110/+183 | |
| 2019-12-23 | Add span information to `ExprKind::Assign` | varkor | -2/+2 | |
| 2019-12-23 | Add the full issue reference to equality constraints in `where` clauses | varkor | -2/+8 | |
| 2019-12-22 | Format the world | Mark Rousskov | -655/+666 | |
| 2019-12-21 | Use Arena inside hir::Body. | Camille GILLOT | -5/+5 | |
| 2019-12-21 | Use Arena inside hir::Mod. | Camille GILLOT | -1/+1 | |
| 2019-12-21 | Use Arena inside hir::StructField. | Camille GILLOT | -3/+3 | |
| 2019-12-21 | Use Arena inside hir::EnumDef. | Camille GILLOT | -5/+5 | |
| 2019-12-21 | Use Arena inside hir::ImplItem. | Camille GILLOT | -5/+5 | |
| 2019-12-21 | Use Arena inside hir::TraitItem. | Camille GILLOT | -5/+5 | |
| 2019-12-21 | Use Arena inside hir::ForeignItem. | Camille GILLOT | -3/+3 | |
| 2019-12-21 | Handle Attributes in arena. | Camille GILLOT | -1/+1 | |
| 2019-12-21 | Use Arena inside hir::Item. | Camille GILLOT | -11/+11 | |
| 2019-12-21 | Use Arena inside hir::Crate. | Camille GILLOT | -5/+5 | |
| 2019-12-20 | 1. ast::Mutability::{Mutable -> Mut, Immutable -> Not}. | Mazdak Farrokhzad | -4/+4 | |
| 2. mir::Mutability -> ast::Mutability. | ||||
| 2019-12-20 | Rollup merge of #67131 - Centril:item-merge, r=petrochenkov | Mazdak Farrokhzad | -35/+130 | |
| Merge `TraitItem` & `ImplItem into `AssocItem` In this PR we: - Merge `{Trait,Impl}Item{Kind?}` into `AssocItem{Kind?}` as discussed in https://github.com/rust-lang/rust/issues/65041#issuecomment-538105286. - This is done by using the cover grammar of both forms. - In particular, it requires that we syntactically allow (under `#[cfg(FALSE)]`): - `default`ness on `trait` items, - `impl` items without a body / definition (`const`, `type`, and `fn`), - and associated `type`s in `impl`s with bounds, e.g., `type Foo: Ord;`. - The syntactic restrictions are replaced by semantic ones in `ast_validation`. - Move syntactic restrictions around C-variadic parameters from the parser into `ast_validation`: - `fn`s in all contexts now syntactically allow `...`, - `...` can occur anywhere in the list syntactically (`fn foo(..., x: usize) {}`), - and `...` can be the sole parameter (`fn foo(...) {}`. r? @petrochenkov | ||||
| 2019-12-13 | Use better name for local containing required feature gates | Dylan MacKenzie | -5/+5 | |
| 2019-12-13 | Replace `Index` impl with `enabled` method | Dylan MacKenzie | -2/+2 | |
| 2019-12-13 | Apply suggestions from review | Dylan MacKenzie | -5/+5 | |
| 2019-12-13 | Improve comment | Dylan MacKenzie | -2/+2 | |
| 2019-12-13 | Restructue HIR const-checker to handle features with multiple gates | Dylan MacKenzie | -19/+69 | |
| 2019-12-12 | `AssocImplKind::{Method -> Fn}`. | Mazdak Farrokhzad | -4/+4 | |
| 2019-12-12 | Remove `ast::{Impl,Trait}{Item,ItemKind}`. | Mazdak Farrokhzad | -3/+3 | |
| 2019-12-12 | More c-variadic errors as semantic restrictions. | Mazdak Farrokhzad | -2/+21 | |
| 2019-12-12 | `ast_validation`: move trait item logic to proper place. | Mazdak Farrokhzad | -20/+23 | |
| 2019-12-12 | Move `allow_c_varadic` logic to `ast_validation`. | Mazdak Farrokhzad | -0/+26 | |
| 2019-12-12 | Unify assoc item visitors more. | Mazdak Farrokhzad | -4/+4 | |
| 2019-12-12 | Unify associated item visitor. | Mazdak Farrokhzad | -9/+9 | |
| 2019-12-12 | parse: refactor fun ret ty & param ty | Mazdak Farrokhzad | -2/+2 | |
| 2019-12-12 | Unify `{Trait,Impl}ItemKind::TyAlias` structures. | Mazdak Farrokhzad | -0/+16 | |
| 2019-12-12 | Use `Option` in `ImplItemKind::Method`. | Mazdak Farrokhzad | -11/+20 | |
| 2019-12-12 | Use `Option` in `ImplItemKind::Const`. | Mazdak Farrokhzad | -6/+20 | |
| 2019-12-12 | Alias `TraitItem` & `ImplItem`. | Mazdak Farrokhzad | -0/+9 | |
| Allow defaultness on trait items syntactically. | ||||
| 2019-12-07 | Simplify `check_decl_no_pat`. | Mazdak Farrokhzad | -5/+5 | |
| 2019-12-02 | syntax: Remove redundant span from `ast::Mac` | Vadim Petrochenkov | -8/+0 | |
| Also remove a couple of redundant `visit_mac` asserts | ||||
| 2019-11-30 | move GateIssue to rustc_feature & simplify emit_feature_err | Mazdak Farrokhzad | -8/+2 | |
| 2019-11-30 | move is_builtin_attr to syntax::attr | Mazdak Farrokhzad | -2/+1 | |
| 2019-11-30 | introduce crate rustc_feature and move active, accepted, and removed to it | Mazdak Farrokhzad | -1/+3 | |
| 2019-11-26 | Rollup merge of #66754 - estebank:rustdoc-capitalization, r=Dylan-DPC | Tyler Mandry | -2/+2 | |
| Various tweaks to diagnostic output | ||||
| 2019-11-25 | Tweak bad `continue` error | Esteban Küber | -2/+2 | |
| 2019-11-24 | Add raw address of expressions to the AST and HIR | Matthew Jasper | -1/+1 | |
| 2019-11-23 | Auto merge of #66507 - ecstatic-morse:const-if-match, r=oli-obk | bors | -25/+73 | |
| Enable `if` and `match` in constants behind a feature flag This PR is an initial implementation of #49146. It introduces a `const_if_match` feature flag and does the following if it is enabled: - Allows `Downcast` projections, `SwitchInt` terminators and `FakeRead`s for matched places through the MIR const-checker. - Allows `if` and `match` expressions through the HIR const-checker. - Stops converting `&&` to `&` and `||` to `|` in `const` and `static` items. As a result, the following operations are now allowed in a const context behind the feature flag: - `if` and `match` - short circuiting logic operators (`&&` and `||`) - the `assert` and `debug_assert` macros (if the `const_panic` feature flag is also enabled) However, the following operations remain forbidden: - `while`, `loop` and `for` (see #52000) - the `?` operator (calls `From::from` on its error variant) - the `assert_eq` and `assert_ne` macros, along with their `debug` variants (calls `fmt::Debug`) This PR is possible now that we use dataflow for const qualification (see #64470 and #66385). r? @oli-obk cc @rust-lang/wg-const-eval @eddyb | ||||
| 2019-11-22 | Rollup merge of #66183 - Centril:empty-vis-trait-decl, r=petrochenkov | Mazdak Farrokhzad | -0/+6 | |
| *Syntactically* permit visibilities on trait items & enum variants Fixes #65041 Suppose we have `$vis trait_item` or `$vis enum_variant` and `$vis` is a `:vis` macro fragment. Before this PR, this would fail to parse. This is now instead allowed as per language team consensus in https://github.com/rust-lang/rust/issues/65041#issuecomment-538105286. (See added tests for elaboration.) Moreover, we now also permit visibility modifiers on trait items & enum variants *syntactically* but reject them with semantic checks (in `ast_validation`): ```rust #[cfg(FALSE)] trait Foo { pub fn bar(); } // OK #[cfg(FALSE)] enum E { pub U } // OK ``` | ||||
| 2019-11-21 | Suggest `const_if_match` on nightly | Dylan MacKenzie | -19/+70 | |
| 2019-11-21 | Hold a `TyCtxt` in the HIR const-checker | Dylan MacKenzie | -10/+7 | |
| 2019-11-21 | Add feature gate for const `if` and `match` | Dylan MacKenzie | -1/+1 | |
| 2019-11-21 | reduce size of hir::ExprKind | Mazdak Farrokhzad | -13/+17 | |
| 2019-11-20 | Rollup merge of #66535 - estebank:issue-62480, r=matthewjasper | Mazdak Farrokhzad | -3/+10 | |
| Avoid ICE when `break`ing to an unreachable label Fix #62480. | ||||
| 2019-11-18 | Avoid ICE when `break`ing to an unreachable label | Esteban Küber | -3/+10 | |
| 2019-11-18 | Reword help and add test | Esteban Küber | -6/+4 | |
