diff options
| author | bors <bors@rust-lang.org> | 2023-11-01 14:17:56 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-01 14:17:56 +0000 |
| commit | 146dafa26277c873172f555017b970ef006d302a (patch) | |
| tree | 876ed8c65789f5eaeb01332ce8f2a6d034a471df /compiler/rustc_mir_transform/src/coverage/tests.rs | |
| parent | 11cd1f00268061dff447bc0df3d679b35d460875 (diff) | |
| parent | e742f809f68d571a28b7c9153366194e47714b65 (diff) | |
| download | rust-146dafa26277c873172f555017b970ef006d302a.tar.gz rust-146dafa26277c873172f555017b970ef006d302a.zip | |
Auto merge of #114208 - GKFX:offset_of_enum, r=wesleywiser
Support enum variants in offset_of! This MR implements support for navigating through enum variants in `offset_of!`, placing the enum variant name in the second argument to `offset_of!`. The RFC placed it in the first argument, but I think it interacts better with nested field access in the second, as you can then write things like ```rust offset_of!(Type, field.Variant.field) ``` Alternatively, a syntactic distinction could be made between variants and fields (e.g. `field::Variant.field`) but I'm not convinced this would be helpful. [RFC 3308 # Enum Support](https://rust-lang.github.io/rfcs/3308-offset_of.html#enum-support-offset_ofsomeenumstructvariant-field_on_variant) Tracking Issue #106655.
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/tests.rs')
0 files changed, 0 insertions, 0 deletions
