diff options
| author | bors <bors@rust-lang.org> | 2021-10-11 04:31:47 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-10-11 04:31:47 +0000 |
| commit | 775b6daf0f4120cf0ba8f8a6475f23e9b6fffd91 (patch) | |
| tree | 65d1df58a718d76e750c0bbff3bd8bd8e6bfa56a /src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs | |
| parent | 583170aec889933d5bf4ef58aa0326928608efe4 (diff) | |
| parent | 7033f75a49f43b9cd0db62b34dcfaa3307e0cbcd (diff) | |
| download | rust-775b6daf0f4120cf0ba8f8a6475f23e9b6fffd91.tar.gz rust-775b6daf0f4120cf0ba8f8a6475f23e9b6fffd91.zip | |
Auto merge of #89597 - michaelwoerister:improve-vtable-debuginfo, r=wesleywiser
Create more accurate debuginfo for vtables. Before this PR all vtables would have the same name (`"vtable"`) in debuginfo. Now they get an unambiguous name that identifies the implementing type and the trait that is being implemented. This is only one of several possible improvements: - This PR describes vtables as arrays of `*const u8` pointers. It would nice to describe them as structs where function pointer is represented by a field with a name indicative of the method it maps to. However, this requires coming up with a naming scheme that avoids clashes between methods with the same name (which is possible if the vtable contains multiple traits). - The PR does not update the debuginfo we generate for the vtable-pointer field in a fat `dyn` pointer. Right now there does not seem to be an easy way of getting ahold of a vtable-layout without also knowing the concrete self-type of a trait object. r? `@wesleywiser`
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs')
0 files changed, 0 insertions, 0 deletions