1
Fork 0

switch __field__ hack to <unnamed_field>

avoids conflict with fields actually named `__field__`
This commit is contained in:
Daniel Micay 2013-09-02 04:59:51 -04:00
parent 331d2d6d31
commit 67a8ea521a
2 changed files with 3 additions and 2 deletions

View file

@ -436,7 +436,7 @@ fn mk_fresh_ident_interner() -> @ident_interner {
"blk", // 26
"static", // 27
"__foreign_mod__", // 28
"__field__", // 29
"<unnamed_field>", // 29
"C", // 30
"Self", // 31

View file

@ -34,7 +34,8 @@
// 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 NoPadding32(i32, f32, u32);