switch __field__ hack to <unnamed_field>
avoids conflict with fields actually named `__field__`
This commit is contained in:
@@ -436,7 +436,7 @@ fn mk_fresh_ident_interner() -> @ident_interner {
|
|||||||
"blk", // 26
|
"blk", // 26
|
||||||
"static", // 27
|
"static", // 27
|
||||||
"__foreign_mod__", // 28
|
"__foreign_mod__", // 28
|
||||||
"__field__", // 29
|
"<unnamed_field>", // 29
|
||||||
"C", // 30
|
"C", // 30
|
||||||
"Self", // 31
|
"Self", // 31
|
||||||
|
|
||||||
|
|||||||
@@ -34,7 +34,8 @@
|
|||||||
|
|
||||||
|
|
||||||
// This test case mainly makes sure that no field names are generated for tuple structs (as opposed
|
// This test case mainly makes sure that no field names are generated for tuple structs (as opposed
|
||||||
// to all fields having the name "__field__"). Otherwise they are handled the same a normal structs.
|
// to all fields having the name "<unnamed_field>"). Otherwise they are handled the same a normal
|
||||||
|
// structs.
|
||||||
|
|
||||||
struct NoPadding16(u16, i16);
|
struct NoPadding16(u16, i16);
|
||||||
struct NoPadding32(i32, f32, u32);
|
struct NoPadding32(i32, f32, u32);
|
||||||
|
|||||||
Reference in New Issue
Block a user