| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-06-20 | Rename ty_param_bound to generic_bound | varkor | -13/+13 | |
| 2018-06-20 | Make GenericBound explicit | varkor | -5/+5 | |
| 2018-06-20 | Rename ParamBound(s) to GenericBound(s) | varkor | -6/+6 | |
| 2018-06-20 | Rename TraitTyParamBound to ParamBound::Trait | varkor | -4/+4 | |
| 2018-06-20 | Fix HasAttrs support for GenericParam | varkor | -1/+1 | |
| 2018-06-20 | Remove name from GenericParamKind::Lifetime | varkor | -3/+1 | |
| 2018-06-20 | Use ParamBounds in WhereRegionPredicate | varkor | -6/+4 | |
| 2018-06-20 | Lift bounds into GenericParam | varkor | -10/+12 | |
| 2018-06-20 | Rename structures in ast | varkor | -14/+14 | |
| 2018-06-20 | Refactor ast::GenericParam as a struct | varkor | -25/+25 | |
| 2018-06-20 | Rename ast::GenericParam and ast::GenericArg | varkor | -12/+11 | |
| It's so confusing to have everything having the same name, at least while refactoring. | ||||
| 2018-06-20 | Rename "parameter" to "arg" | varkor | -15/+15 | |
| 2018-06-20 | Rename *Parameter to *Param | varkor | -4/+4 | |
| 2018-06-20 | Consolidate PathParameters and AngleBracketedParameterData | varkor | -9/+11 | |
| 2018-06-19 | Update error code numbers | Esteban Küber | -2/+2 | |
| 2018-06-19 | Fix tidy and remove unused method | Esteban Küber | -2/+2 | |
| 2018-06-19 | Point to previous line for single expected token | Esteban Küber | -1/+20 | |
| 2018-06-19 | Add message to `rustc_on_unimplemented` attributes in core | Esteban Küber | -8/+0 | |
| 2018-06-19 | Add code to incorrect `pub` restriction error | Esteban Küber | -3/+4 | |
| 2018-06-19 | Add code to `invalid ABI` error | Esteban Küber | -5/+8 | |
| 2018-06-19 | Do not consume semicolon twice while parsing local statement | Seiichi Uchida | -1/+1 | |
| 2018-06-19 | Auto merge of #51278 - EPashkin:fix_mod_with_multilevel_paths_on_windows, ↵ | bors | -1/+13 | |
| r=nikomatsakis Fix processing mod with multi-level path on Windows Fix error in [rustfmt](https://github.com/rust-lang-nursery/rustfmt/issues/1754) because libsyntax can not handle `mod` with multilevel path on Windows. Alternative is do almost same in https://github.com/rust-lang/rust/blob/master/src/libstd/sys/windows/fs.rs#L717 to allow work on paths with different separators, Ex. "\\\\?\\c:\\windows/temp" | ||||
| 2018-06-17 | Auto merge of #51549 - PSeitz:patch-1, r=kennytm | bors | -2/+2 | |
| Follow up to #51508, make parse_block public instead parse_block_expr This is an follow up to #51508 I mistakenly made parse_block_expr public instead of parse_block. This fixes this. | ||||
| 2018-06-16 | Follow up on https://github.com/rust-lang/rust/pull/51508, make parse_block ↵ | PSeitz | -2/+2 | |
| public instead parse_block_expr This is an follow up to #51508 I mistakenly made parse_block_expr public instead of parse_block. This fixes this. | ||||
| 2018-06-14 | create multiple HIR items for a use statement | QuietMisdreavus | -1/+1 | |
| 2018-06-12 | Rollup merge of #51502 - jebrosen:pub_parse_methods, r=Mark-Simulacrum | Mark Rousskov | -2/+2 | |
| Make parse_seq_to_end and parse_path public (see SergioBenitez/Rocket#660, rust-lang/rust#51265) Rocket currently uses `parse_seq_to_end` and `parse_path` in its codegen macros. Assuming I tested correctly, this is the minimal set of methods that are currently necessary to build Rocket again. I would be happy to add documentation of this and Rocket's other usages, if desired. | ||||
| 2018-06-12 | Auto merge of #51508 - PSeitz:master, r=Mark-Simulacrum | bors | -2/+2 | |
| Make span_fatal and parse_block public span_fatal and parse_block were made private in #51265. These methods are used in stainless. Related #51498 #51504 | ||||
| 2018-06-11 | Make span_fatal and parse_block public | PSeitz | -2/+2 | |
| span_fatal and parse_block were made private in #51265. These methods are used in stainless. Related #51498 #51504 | ||||
| 2018-06-11 | Make parse_seq_to_end and parse_path public | jeb | -2/+2 | |
| 2018-06-11 | Make parse_ident public | Seiichi Uchida | -1/+1 | |
| 2018-06-10 | Auto merge of #50205 - topecongiro:include-parens-to-type-parameter, ↵ | bors | -8/+9 | |
| r=petrochenkov Include parens to type parameter The motivation of this PR is to fix a bug in rustfmt (cc https://github.com/rust-lang-nursery/rustfmt/issues/2630). | ||||
| 2018-06-10 | Simplify an error handling in the parser | Seiichi Uchida | -6/+2 | |
| 2018-06-10 | Include parens to type parameter | Seiichi Uchida | -2/+7 | |
| 2018-06-09 | Crate-ify and delete unused code in syntax::parse | Mark Simulacrum | -234/+105 | |
| 2018-06-09 | Auto merge of #51068 - Crazycolorz5:pluseqsplitting, r=petrochenkov | bors | -10/+44 | |
| parser: Split `+=` into `+` and `=` where `+` is explicitly requested (such as generics) Added functions in tokens to check whether a token leads with `+`. Used them when parsing to allow for token splitting of `+=` into `+` and `=`. Fixes https://github.com/rust-lang/rust/issues/47856 | ||||
| 2018-06-08 | Rollup merge of #51099 - Crazycolorz5:expectedcloseparen, r=estebank | Mark Rousskov | -2/+7 | |
| Fix Issue 38777 When looking through for a closing bracket in the loop condition, adds them to expecteds. https://github.com/rust-lang/rust/issues/38777 | ||||
| 2018-06-07 | add an explanatory comment | Niko Matsakis | -0/+5 | |
| 2018-06-06 | Auto merge of #51201 - estebank:dotdot, r=petrochenkov | bors | -69/+135 | |
| Accept `..` in incorrect position to avoid further errors We currently give a specific message when encountering a `..` anywhere other than the end of a pattern. Modify the parser to accept it (while still emitting the error) so that we don't also trigger "missing fields in pattern" errors afterwards. Add suggestions to either remove trailing `,` or moving the `..` to the end. Follow up to #49268. | ||||
| 2018-06-05 | Account for comma in suggestion | Esteban Küber | -1/+1 | |
| 2018-06-05 | Improve diagnostics for incorrect `..` usage | Esteban Küber | -79/+135 | |
| When using `..` somewhere other than the end, parse the rest of the pattern correctly while still emitting an error. Add suggestions to either remove trailing `,` or moving the `..` to the end. | ||||
| 2018-06-05 | Accept `..` in incorrect position to avoid further errors | Esteban Küber | -0/+10 | |
| We currently give a specific message when encountering a `..` anywhere other than the end of a pattern. Modify the parser to accept it (while still emitting the error) so that we don't also trigger "missing fields in pattern" errors afterwards. | ||||
| 2018-06-04 | Fixed indentation error. | Crazycolorz5 | -2/+2 | |
| 2018-06-04 | Fixed incorrect check_plus to token.is_like_plus. | Crazycolorz5 | -1/+1 | |
| 2018-06-04 | Tidy fixes. | Crazycolorz5 | -5/+5 | |
| 2018-06-04 | Added is_like_plus to token, and used that in place of equality comparison ↵ | Crazycolorz5 | -9/+22 | |
| to Plus token. | ||||
| 2018-06-04 | Implemented eat_plus and used it in parsing parse_ty_param_bounds_common. | Crazycolorz5 | -1/+22 | |
| 2018-06-01 | Suggest not mutably borrowing a mutable reference | Yaron Tausky | -20/+22 | |
| This commit is concerned with the case where the user tries to mutably borrow a mutable reference, thereby triggering an error. Instead of the existing suggestion to make the binding mutable, the compiler will now suggest to avoid borrowing altogether. | ||||
| 2018-06-01 | Fix processing mod with multi-level path on Windows | Evgenii Pashkin | -1/+8 | |
| 2018-06-01 | Add closing bracket expectation to sequences, modified appropriate test cases. | Crazycolorz5 | -2/+7 | |
| 2018-05-28 | Auto merge of #50724 - zackmdavis:applicability_rush, r=Manishearth | bors | -52/+140 | |
| add suggestion applicabilities to librustc and libsyntax A down payment on #50723. Interested in feedback on whether my `MaybeIncorrect` vs. `MachineApplicable` judgement calls are well-calibrated (and that we have a consensus on what this means). r? @Manishearth cc @killercup @estebank | ||||
