rust/compiler/rustc_parse/src/parser, branch 1.64.0

Revert let_chains stabilization

2022-08-15T07:05:24+00:00

This reverts commit 326646074940222d602f3683d0559088690830f4. It was discovered that they are not implemented correctly, which does not make them ready for stabilization.

Rollup merge of #98796 - compiler-errors:no-semi-if-comma, r=estebank

2022-08-04T20:24:59+00:00

Do not exclusively suggest `;` when `,` is also a choice Fixes #96791

Rollup merge of #99786 - obeis:issue-99625, r=compiler-errors

2022-08-03T20:29:29+00:00

Recover from C++ style `enum struct` Closes #99625

Rollup merge of #100011 - compiler-errors:let-chain-restriction, r=fee1-dead

2022-08-02T05:30:44+00:00

Use Parser's `restrictions` instead of `let_expr_allowed` This also means that the `ALLOW_LET` flag is reset properly for subexpressions, so we can properly deny things like `a && (b && let c = d)`. Also the parser is a tiny bit smaller now. It doesn't reject _all_ bad `let` expr usages, just a bit more. cc `@c410-f3r`

Use expr parse restrictions for let expr parsing

2022-08-01T01:13:16+00:00

Auto merge of #99948 - Dylan-DPC:rollup-ed5136t, r=Dylan-DPC

2022-07-30T17:30:50+00:00

Rollup of 5 pull requests Successful merges: - #99311 (change maybe_body_owned_by to take local def id) - #99862 (Improve type mismatch w/ function signatures) - #99895 (don't call type ascription "cast") - #99900 (remove some manual hash stable impls) - #99903 (Add diagnostic when using public instead of pub) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #99903 - gimbles:pub, r=davidtwco

2022-07-30T15:09:50+00:00

Add diagnostic when using public instead of pub Forwarding from https://github.com/rust-lang/rust/pull/99706 I accidentally broke something(??) in git and the commits in that PR are absolutely not what I did in that branch Anyways, this is the PR for this now. Adding tests again in a minute. cc `@davidtwco`

Auto merge of #99887 - nnethercote:rm-TreeAndSpacing, r=petrochenkov

2022-07-30T14:50:05+00:00

Remove `TreeAndSpacing`. A `TokenStream` contains a `Lrc>`. But this is not quite right. `Spacing` makes sense for `TokenTree::Token`, but does not make sense for `TokenTree::Delimited`, because a `TokenTree::Delimited` cannot be joined with another `TokenTree`. This commit fixes this problem, by adding `Spacing` to `TokenTree::Token`, changing `TokenStream` to contain a `Lrc>`, and removing the `TreeAndSpacing` typedef. The commit removes these two impls: - `impl From for TokenStream` - `impl From for TreeAndSpacing` These were useful, but also resulted in code with many `.into()` calls that was hard to read, particularly for anyone not highly familiar with the relevant types. This commit makes some other changes to compensate: - `TokenTree::token()` becomes `TokenTree::token_{alone,joint}()`. - `TokenStream::token_{alone,joint}()` are added. - `TokenStream::delimited` is added. This results in things like this: ```rust TokenTree::token(token::Semi, stmt.span).into() ``` changing to this: ```rust TokenStream::token_alone(token::Semi, stmt.span) ``` This makes the type of the result, and its spacing, clearer. These changes also simplifies `Cursor` and `CursorRef`, because they no longer need to distinguish between `next` and `next_with_spacing`. r? `@petrochenkov`

Add diagnostic when using public instead of pub

2022-07-29T13:51:30+00:00

Recover from c++ style `enum struct`

2022-07-29T10:56:54+00:00

new error message: `enum` and `struct` are mutually exclusive new suggestion: replace `enum struct` with `enum`