about summary refs log tree commit diff
path: root/crates/parser/src
AgeCommit message (Collapse)AuthorLines
2021-08-22Fix three more (reverse) “a”/“an” typosFrank Steffahn-1/+1
2021-08-13Support `if let` match guardsJonas Schievink-0/+5
2021-08-04Split the testJade-2/+10
2021-08-03Support exclusive_range_patternJade-3/+7
Fix #9779
2021-08-03tree-wide: fix rustdoc warnings, add some linksJade-13/+17
2021-07-30SimplifyLukas Wirth-4/+2
2021-07-29Attach comma token to MATCH_ARM instead of MATCH_ARM_LISTLukas Wirth-16/+16
2021-07-26Fix generic_arg not parsing opt_generic_arg_list properly in arg listsLukas Wirth-4/+3
2021-07-21Fix some more basic clippy lintsLukas Wirth-12/+8
2021-07-20Restrict completions inside visibility modifiersLukas Wirth-1/+1
2021-07-18Merge #9619bors[bot]-11/+53
9619: Support GATs for associated type arg parsing r=Veykril a=Veykril Fixes #9602 Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2021-07-18Support GATs for associated type arg parsingLukas Wirth-11/+53
2021-07-17feat: improve parser error recovery for function parametersAleksey Kladov-6/+24
2021-07-03internal: overhaul code generationAleksey Kladov-1/+1
* Keep codegen adjacent to the relevant crates. * Remove codgen deps from xtask, speeding-up from-source installation. This regresses the release process a bit, as it now needs to run the tests (and, by extension, compile the code).
2021-06-17Complete `repr` attribute parametersLukas Wirth-2/+1
2021-06-14Merge #9260bors[bot]-1/+1
9260: tree-wide: make rustdoc links spiky so they are clickable r=matklad a=lf- Rustdoc was complaining about these while I was running with --document-private-items and I figure they should be fixed. Co-authored-by: Jade <software@lfcode.ca>
2021-06-13tree-wide: make rustdoc links spiky so they are clickableJade-1/+1
2021-06-11Update ungrammarJonas Schievink-1/+4
2021-06-03Apply more clippy suggestions and update generatedClemens Wasser-106/+23
2021-06-03Apply a few clippy suggestionsClemens Wasser-28/+109
2021-05-22Add even more docsAleksey Kladov-30/+4
2021-05-08Add `=` to pattern recoveryLukas Wirth-1/+1
2021-04-29Parse const param defaultsJonas Schievink-0/+42
2021-04-29Correctly parse negated literals as const argsJonas Schievink-0/+9
2021-04-21Parse outer atttributes for RecordPatFieldLukas Wirth-2/+4
2021-04-17hir_ty: Expand macros at type positioncynecx-3/+7
2021-04-17Handle extended key value attr in mbeEdwin Cheng-48/+17
2021-03-19Parse extended_key_value_attributesLukas Wirth-2/+2
2021-03-17Correctly parse attributes on fn parametersJonas Schievink-7/+22
2021-03-16Fix macro expansion for statements w/o semicolonEdwin Cheng-6/+6
2021-03-12Fix remaining references to `cargo xtask codegen`Lukas Wirth-1/+1
2021-03-06Fix fail to parse :: for meta in mbeEdwin Cheng-1/+2
2021-02-15Specialization for async traitsArnaud-0/+28
2021-02-12Pin Rust to 1.49.0 on CIJonas Schievink-5/+6
2021-01-24Add validation for mutable const itemsLukas Wirth-1/+1
2021-01-18Merge #7341bors[bot]-1/+4
7341: Fix warnings when running `cargo doc --document-private-items` r=Veykril a=jyn514 These were the warnings previously: <details> ``` warning: could not parse code block as Rust code --> crates/stdx/src/lib.rs:137:9 | 137 | /// ∀ x in slice[..idx]: pred(x) | _________^ 138 | | /// && ∀ x in slice[idx..]: !pred(x) | |____^ | = note: error from rustc: unknown start of token: \u{2200} warning: 1 warning emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted ``` </details> This does *not* fix the following warning, because it is actually rust code and rustdoc is being over eager: ``` warning: Rust code block is empty --> crates/parser/src/grammar.rs:16:5 | 16 | //! ``` | _____^ 17 | | //! // test function_with_zero_parameters 18 | | //! // fn foo() {} 19 | | //! ``` | |_______^ | help: mark blocks that do not contain Rust code as text | 16 | //! ```text | ^^^^^^^ ``` https://github.com/rust-lang/rust/pull/79816 should make this configurable so the warning can be `allow`ed. Co-authored-by: Joshua Nelson <jyn514@gmail.com>
2021-01-18Fix warnings when running `cargo doc --document-private-items`Joshua Nelson-1/+4
These were the warnings previously: ``` warning: could not parse code block as Rust code --> crates/stdx/src/lib.rs:137:9 | 137 | /// ∀ x in slice[..idx]: pred(x) | _________^ 138 | | /// && ∀ x in slice[idx..]: !pred(x) | |____^ | = note: error from rustc: unknown start of token: \u{2200} warning: 1 warning emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted ``` This does *not* fix the following warning, because it is actually rust code and rustdoc is being over eager: ``` warning: Rust code block is empty --> crates/parser/src/grammar.rs:16:5 | 16 | //! ``` | _____^ 17 | | //! // test function_with_zero_parameters 18 | | //! // fn foo() {} 19 | | //! ``` | |_______^ | help: mark blocks that do not contain Rust code as text | 16 | //! ```text | ^^^^^^^ ``` https://github.com/rust-lang/rust/pull/79816 should make this configurable so the warning can be `allow`ed.
2021-01-18Parse `impl const Trait`Lukas Wirth-0/+4
2021-01-18Add `MacroType` syntaxJonas Schievink-0/+1
2021-01-18Merge #7291bors[bot]-15/+30
7291: Wrap remaining self/super/crate in Name{Ref} r=matklad a=Veykril That should be the remaining special casing for `self` 🎉 Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2021-01-17Add missing inlinesAleksey Kladov-0/+3
2021-01-15Wrap remaining self/super/crate in Name{Ref}Lukas Wirth-15/+30
2021-01-15Handle self/super/crate in PathSegment as NameRefLukas Wirth-1/+5
2021-01-15Add support for yiled keywordDaiki Ihara-2/+22
2021-01-14Merge #7211bors[bot]-3/+13
7211: Fixed expr meta var after path colons in mbe r=matklad a=edwin0cheng Fixes #7207 Added `L_DOLLAR` in `ITEM_RECOVERY_SET` , but I don't know whether it is a good idea. r? @matklad Co-authored-by: Edwin Cheng <edwin0cheng@gmail.com>
2021-01-10Merge #7218bors[bot]-1/+1
7218: Fix typos r=Veykril a=regexident Apart from the very last commit on this PR (which fixes a public type's name) all changes are non-breaking. Co-authored-by: Vincent Esche <regexident@gmail.com>
2021-01-10Replace SyntaxKind usage with T! macro where applicableLukas Wirth-19/+27
2021-01-10Use T! for bool keywordsLaurențiu Nicola-1/+1
2021-01-10Allow `true` and `false` keywords in const genericsCallym-1/+5
2021-01-10Fixed expr meta var after path colons in mbeEdwin Cheng-3/+13
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 13:56:19 +0000