rust/src/test/ui/structs, branch automation/bors/try https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try 2023-01-11T09:32:08+00:00 Move /src/test to /tests 2023-01-11T09:32:08+00:00 Albert Larsan 74931857+albertlarsan68@users.noreply.github.com 2023-01-05T08:13:28+00:00 urn:sha1:cf2dff2b1e3fa55fa5415d524200070d0d7aacfe Introduce `with_forced_trimmed_paths` 2022-12-10T22:35:40+00:00 Esteban Küber esteban@kuber.com.ar 2022-12-07T04:13:31+00:00 urn:sha1:3ad7131aa1d76f46af8994831b2f950c09d206cd Rollup merge of #105267 - compiler-errors:issue-104613, r=oli-obk 2022-12-07T14:39:06+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-12-07T14:39:06+00:00 urn:sha1:3bcfa4c45940eb9d41493d9d64c0f1dbe7f14f08 Don't ICE in ExprUseVisitor on FRU for non-existent struct Fixes #104613 Fixes #105202 Don't ICE in ExprUseVisitor on FRU for non-existent struct 2022-12-04T18:53:50+00:00 Michael Goulet michael@errs.io 2022-12-04T18:53:50+00:00 urn:sha1:d442c015d6d688460a182947e797f4bf69876044 While parsing enum variant, the error message always disappear 2022-12-02T06:48:52+00:00 Yiming Lei yiming.lei@futurewei.com 2022-11-30T20:01:00+00:00 urn:sha1:0e19fb92e1eb7f91aa5570b2ac782c9a42a6e329 Because the error message that emit out is from main error of parser The information of enum variant disappears while parsing enum variant with error We only check the syntax of expecting token, i.e, in case #103869 It will error it without telling the message that this error is from pasring enum variant. Propagate the sub-error from parsing enum variant to the main error of parser by chaining it with map_err Check the sub-error before emitting the main error of parser and attach it. Fix #103869 Add a detailed note for missing comma in FRU syntax typo 2022-11-18T17:27:55+00:00 Michael Goulet michael@errs.io 2022-11-16T19:10:38+00:00 urn:sha1:bb0cb9ae9fb2dbebc62627a3f1f4326771338535 fix a ui test 2022-09-28T02:42:52+00:00 Takayuki Maeda takoyaki0316@gmail.com 2022-09-28T02:42:52+00:00 urn:sha1:e665d20c020724fa356fef0214e14b4066563a29 improve errors for incomplete functions in struct definitions 2022-09-27T16:03:18+00:00 Takayuki Maeda takoyaki0316@gmail.com 2022-09-27T08:20:55+00:00 urn:sha1:d7b6bd8f131a269102662ff249e916d6f7069f97 add a label to struct/enum/union ident name 2022-09-27T01:28:50+00:00 Takayuki Maeda takoyaki0316@gmail.com 2022-09-26T14:13:38+00:00 urn:sha1:4f44dee50129ebd5da77a14a786849973f47b38f Auto merge of #100865 - compiler-errors:parent-substs-still, r=cjgillot 2022-09-25T12:00:37+00:00 bors bors@rust-lang.org 2022-09-25T12:00:37+00:00 urn:sha1:4652f5eb25b76c24fc40b7267d87a07d5876901f Don't drop parent substs when we have no generic parameters in `create_substs_for_ast_path` This bug is being shadowed by an explicit check for `generics.params.is_empty()` in the only parent caller that could trigger it (`create_substs_for_associated_item`). I triggered it on another branch where I'm messing around with astconv stuff. Also, the second commit simplifies `create_substs_for_associated_item`. Removing that explicit check I mentioned above^ and also the special case call to `Astconv::prohibit_generics` causes the UI test `src/test/ui/structs/struct-path-associated-type.stderr` to change, but I think that it's clearer now. The suggestion to remove the generics is actually useful.