diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-03-15 17:15:52 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-15 17:15:52 +0100 |
| commit | e755f2c7cdf8636f53243f2fdaffab2a87c5a3c5 (patch) | |
| tree | 57e06d8637ffae44b89724db3f43a8aa871ebdd2 /library/std/src/sys/unix/process/process_unix.rs | |
| parent | be52b4af5ec7e49572cb16519b7e144d6bcb051d (diff) | |
| parent | 5cd8a2addaf4aae55c52fb9af5fdb36243295070 (diff) | |
| download | rust-e755f2c7cdf8636f53243f2fdaffab2a87c5a3c5.tar.gz rust-e755f2c7cdf8636f53243f2fdaffab2a87c5a3c5.zip | |
Rollup merge of #94810 - michaelwoerister:fix-trait-pointer-debuginfo-names, r=wesleywiser
debuginfo: Fix bug in type name generation for dyn types with associated types but no other generic arguments. For types like `&dyn Future<Output=bool>` the compiler currently emits invalid types names in debuginfo. This PR fixes this. Before: ```txt // DWARF &dyn core::future::future::Future, Output=bool> // CodeView ref$<dyn$<core::future::future::Future,assoc$<Output,bool> > > > ``` After: ```txt // DWARF &dyn core::future::future::Future<Output=bool> // CodeView ref$<dyn$<core::future::future::Future<assoc$<Output,bool> > > > ``` These syntactically incorrect type names can cause downstream tools (e.g. debugger extensions) crash when trying to parse them. r? `@wesleywiser`
Diffstat (limited to 'library/std/src/sys/unix/process/process_unix.rs')
0 files changed, 0 insertions, 0 deletions