about summary refs log tree commit diff
path: root/src/librustc_parse/parser/generics.rs
AgeCommit message (Collapse)AuthorLines
2020-08-30mv compiler to compiler/mark-292/+0
2020-08-17rust_ast::ast => rustc_astUjjwal Sharma-1/+3
2020-08-05impl reviewBastian Kauschke-1/+1
2020-06-23Record span of `const` kw in GenericParamKindAyaz Hafiz-3/+3
Context: this is needed to fix https://github.com/rust-lang/rustfmt/issues/4263, which currently records the span of a const generic param incorrectly because the location of the `const` kw is not known. I am not sure how to add tests for this; any guidance in how to do so would be appreciated :slightly_smiling_face:
2020-06-08Don't lose empty `where` clause when pretty-printingAaron Hill-2/+7
Previously, we would parse `struct Foo where;` and `struct Foo;` identically, leading to an 'empty' `where` clause being omitted during pretty printing. This will cause us to lose spans when proc-macros involved, since we will have a collected `where` token that does not appear in the pretty-printed item. We now explicitly track the presence of a `where` token during parsing, so that we can distinguish between `struct Foo where;` and `struct Foo;` during pretty-printing
2020-04-22Rollup merge of #71256 - cuviper:must_use_replace, r=estebankDylan DPC-1/+1
Lint must_use on mem::replace This adds a hint on `mem::replace`, "if you don't need the old value, you can just assign the new value directly". This is in similar spirit to the `must_use` on `ManuallyDrop::take`.
2020-04-18remove build warningsTshepang Lekhonkhobe-1/+1
Code blocks that are not annotated are assumed to be Rust
2020-04-17Fix unused results from mem::replaceJosh Stone-1/+1
2020-03-21recover on `for<'a> |...| body` closures.Mazdak Farrokhzad-11/+8
2020-03-01Rollup merge of #69579 - petrochenkov:noprevspan, r=CentrilYuki Okushi-12/+16
parser: Remove `Parser::prev_span` Follow-up to https://github.com/rust-lang/rust/pull/69384. r? @Centril
2020-02-29Rename `syntax` to `rustc_ast` in source codeVadim Petrochenkov-2/+2
2020-02-29parser: `prev_span` -> `prev_token.span`Vadim Petrochenkov-12/+16
2020-02-29Auto merge of #69255 - estebank:e0599-details, r=varkorbors-2/+4
Add more context to E0599 errors Point at the intermediary unfulfilled trait bounds. Fix #52523, fix #61661, cc #36513, fix #68131, fix #64417, fix #61768, cc #57457, cc #9082, fix #57994, cc #64934, cc #65149.
2020-02-28Suggest constraining type parametersEsteban Küber-2/+4
2020-02-27Remove unneeded calls to format!()Björn Steinbrink-9/+6
2020-02-02Use more appropriate spans on object unsafe traits and provide structured ↵Esteban Küber-1/+1
suggestions when possible
2020-01-09Extend support of `_` in type parametersEsteban Küber-1/+1
- Account for `impl Trait<_>`. - Provide a reasonable `Span` for empty `Generics` in `impl`s. - Account for `fn foo<_>(_: _) {}` to suggest `fn foo<T>(_: T) {}`. - Fix #67995.
2020-01-02Normalize `syntax::source_map` imports.Mazdak Farrokhzad-1/+1
2020-01-01Rename `syntax_pos` to `rustc_span` in source codeVadim Petrochenkov-1/+1
2019-12-22Format the worldMark Rousskov-68/+45
2019-12-05rustc_parser: cleanup importsMazdak Farrokhzad-1/+1
2019-11-10move syntax::parse -> librustc_parseMazdak Farrokhzad-0/+308
also move MACRO_ARGUMENTS -> librustc_parse