diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2021-05-08 01:06:22 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-08 01:06:22 +0200 |
| commit | eb36bc666a4e1e8b6f54f50f275ae10a4c22c77f (patch) | |
| tree | c5f0802f19737d8c278cee99cf8ba8be804bb26c /tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs | |
| parent | 770792ff8d1ec542e78e77876ac936f43ffb8e05 (diff) | |
| parent | 6717f81b96aca75f5b811104ae75620274dad35d (diff) | |
| download | rust-eb36bc666a4e1e8b6f54f50f275ae10a4c22c77f.tar.gz rust-eb36bc666a4e1e8b6f54f50f275ae10a4c22c77f.zip | |
Rollup merge of #76808 - LeSeulArtichaut:diagnose-functions-struct, r=jackh726
Improve diagnostics for functions in `struct` definitions Tries to implement #76421. This is probably going to need unit tests, but I wanted to hear from review all the cases tests should cover. I'd like to follow up with the "mechanically applicable suggestion here that adds an impl block" step, but I'd need guidance. My idea for now would be to try to parse a function, and if that succeeds, create a dummy `ast::Item` impl block to then format it using `pprust`. Would that be a viable approach? Is there a better alternative? r? `@matklad` cc `@estebank`
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs')
0 files changed, 0 insertions, 0 deletions