rust/compiler/rustc_parse/src/parser/expr.rs, branch 1.56.0

Rollup merge of #88450 - notriddle:notriddle/maybe_whole_expr, r=cjgillot

2021-08-31T08:41:22+00:00

fix(rustc_parse): correct span in `maybe_whole_expr!` Fixes #87812

Auto merge of #88262 - klensy:pprust-cow, r=nagisa

2021-08-29T17:46:29+00:00

Cow'ify some pprust methods Reduce number of potential needless de/allocations by using `Cow<'static, str>` instead of explicit `String` type.

fix(rustc_parse): incorrect span information for macro path expr

2021-08-29T03:56:55+00:00

Old error output: 3 | let _: usize = $f; | ----- ^ expected `usize`, found struct `Baz` | | | expected due to this New error output: 3 | let _: usize = $f; | ----- ^^ expected `usize`, found struct `Baz` | | | expected due to this

fix(rustc_parse): incorrect span information for macro block expr

2021-08-29T00:59:00+00:00

Old error output: = note: this warning originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info) help: wrap this expression in parentheses | 4 | break '_l $f(;) | ^ ^ New error output: = note: this warning originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info) help: wrap this expression in parentheses | 4 | break '_l ($f); | ^ ^

Convert some functions to return Cow<'static,str> instead of String to reduce potential reallocations

2021-08-24T21:24:44+00:00

Fix typos “a”→“an”

2021-08-22T13:35:11+00:00

Introduce hir::ExprKind::Let - Take 2

2021-08-15T19:18:26+00:00

Require parentheses to avoid confusions around labeled break and loop expressions

2021-07-31T17:10:58+00:00

Use multispan suggestions more often

2021-07-30T16:26:31+00:00

* Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often

Auto merge of #87071 - inquisitivecrystal:inclusive-range, r=estebank

2021-07-18T05:58:16+00:00

Add diagnostics for mistyped inclusive range Inclusive ranges are correctly typed as `..=`. However, it's quite easy to think of it as being like `==`, and type `..==` instead. This PR adds helpful diagnostics for this case. Resolves #86395 (there are some other cases there, but I think those should probably have separate issues). r? `@estebank`