diff options
| author | bors <bors@rust-lang.org> | 2022-02-02 12:37:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-02-02 12:37:28 +0000 |
| commit | dca1e7aa5a8ac05ddaea731f4eab20de91acb46b (patch) | |
| tree | 998630298a1ad039ae3be5f6fa34a80ddee06c15 /library/std/src | |
| parent | 250384edc5d78533e993f38c60d64e42b21684b2 (diff) | |
| parent | fd7557b7ee454058fff84b556892adbef89f7d52 (diff) | |
| download | rust-dca1e7aa5a8ac05ddaea731f4eab20de91acb46b.tar.gz rust-dca1e7aa5a8ac05ddaea731f4eab20de91acb46b.zip | |
Auto merge of #93154 - michaelwoerister:fix-generic-closure-and-generator-debuginfo, r=wesleywiser
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo.
Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name.
This commit also emits `{closure_env#0}` as the name of these types in order to disambiguate them from the accompanying closure function (which keeps being called `{closure#0}`). Previously both were assigned the same name.
NOTE: Changing debuginfo names like this can break pretty printers and other debugger plugins. I think it's OK in this particular case because the names we are changing were ambiguous anyway. In general though it would be great to have a process for doing changes like these.
Diffstat (limited to 'library/std/src')
0 files changed, 0 insertions, 0 deletions