rust/compiler/rustc_parse/src/parser/expr.rs, branch 1.57.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.57.02021-10-07T20:31:33+00:00some clippy::perf fixes2021-10-07T20:31:33+00:00Matthias Krügermatthias.krueger@famsik.de2021-10-07T20:31:33+00:00urn:sha1:ff6601e0fc4dd05e337ebc4e0d3c741a0ef26078Use `TokenKind::similar_tokens()`2021-10-04T20:13:00+00:00Fabian Wolfffabian.wolff@alumni.ethz.ch2021-10-04T20:13:00+00:00urn:sha1:079c075f24d2aae84cd6715f350cf56420816f63Try to recover from a `=>` -> `=` or `->` typo in a match arm2021-10-03T12:14:35+00:00Fabian Wolfffabian.wolff@alumni.ethz.ch2021-10-03T12:14:35+00:00urn:sha1:cf19131cb356591d27dded5bdb1d00df1bd077c9Rollup merge of #89023 - Wardenfar:issue-85066, r=nagisa2021-09-24T00:31:42+00:00Jubilee46493976+workingjubilee@users.noreply.github.com2021-09-24T00:31:42+00:00urn:sha1:5da2f460b36988d5e0226412080769bafd94eb3c
Resolve issue : Somewhat confusing error with extended_key_value_attributes
Fixes #85066
Rollup merge of #89046 - oli-obk:fix_oflo, r=estebank2021-09-22T17:03:22+00:00the8472the8472@users.noreply.github.com2021-09-22T17:03:22+00:00urn:sha1:5948a7b40799d0c0ab4dd171375a335402686ff6
"Fix" an overflow in byte position math
r? `@estebank`
help! I fixed the ICE only to brick the diagnostic.
I mean, it was wrong previously (using an already expanded macro span), but it is really bad now XD
Add some more tracing2021-09-20T15:24:47+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2021-09-20T15:24:47+00:00urn:sha1:428138071748e81eb67bb090cb9cd3f78299442bSuggest replacing braces for brackets on array-esque invalid block expr2021-09-19T11:01:23+00:00Hirochika Matsumotogit@hkmatsumoto.com2021-08-06T19:34:29+00:00urn:sha1:21eff8f050b80e28309f72f659339ecfba2e0344
Newcomers may write `{1, 2, 3}` for making arrays, and the current error
message is not informative enough to quickly convince them what is
needed to fix the error.
This PR implements a diagnostic for this case, and its output looks like
this:
```text
error: this code is interpreted as a block expression, not an array
--> src/lib.rs:1:22
|
1 | const FOO: [u8; 3] = {
| ______________________^
2 | | 1, 2, 3
3 | | };
| |_^
|
= note: to define an array, one would use square brackets instead of curly braces
help: try using [] instead of {}
|
1 | const FOO: [u8; 3] = [
2 | 1, 2, 3
3 | ];
|
```
Fix #87672
Resolve issue 850662021-09-19T08:53:49+00:00Theotheo.emeriau@gmail.com2021-09-16T19:00:11+00:00urn:sha1:250a3e482f125e96b37d66d6d87be7b09436be5c
Fix : use struct_dummy
Fix different os messages
Use `multipart_suggestion`2021-09-17T04:39:26+00:00Yuki Okushiyuki.okushi@huawei.com2021-09-17T04:39:26+00:00urn:sha1:e9bf73cb2b025e188787683f1423177a9102d260Rollup merge of #88729 - estebank:struct-literal-using-parens, r=oli-obk2021-09-16T17:57:18+00:00Manish Goregaokarmanishsmail@gmail.com2021-09-16T17:57:18+00:00urn:sha1:2c7d48b9003d7f6f3babd9fa0b3fc1ba94df5ec1
Recover from `Foo(a: 1, b: 2)`
Detect likely `struct` literal using parentheses as delimiters and emit
targeted suggestion instead of type ascription parse error.
Fix #61326.