|
| 1 | +//! See #60210. |
| 2 | +//! |
| 3 | +//! Check that we hard error on invalid suffixes in tuple indexing subexpressions and struct numeral |
| 4 | +//! field names. |
| 5 | +
|
| 6 | +struct X(i32,i32,i32); |
| 7 | + |
| 8 | +fn main() { |
| 9 | + let tup_struct = X(1, 2, 3); |
| 10 | + let invalid_tup_struct_suffix = tup_struct.0suffix; |
| 11 | + //~^ ERROR suffixes on a tuple index are invalid |
| 12 | + let previous_carve_out_tup_struct_suffix = tup_struct.0i32; |
| 13 | + //~^ ERROR suffixes on a tuple index are invalid |
| 14 | + |
| 15 | + let tup = (1, 2, 3); |
| 16 | + let invalid_tup_suffix = tup.0suffix; |
| 17 | + //~^ ERROR suffixes on a tuple index are invalid |
| 18 | + let previous_carve_out_tup_suffix = tup.0u32; |
| 19 | + //~^ ERROR suffixes on a tuple index are invalid |
| 20 | + |
| 21 | + numeral_struct_field_name_suffix_invalid(); |
| 22 | + numeral_struct_field_name_suffix_previous_carve_out(); |
| 23 | +} |
| 24 | + |
| 25 | +// Previously, there were very limited carve outs as a ecosystem impact mitigation implemented in |
| 26 | +// #60186. *Only* `{i,u}{32,usize}` suffixes were temporarily accepted. Now, they all hard error. |
| 27 | +fn previous_carve_outs() { |
| 28 | + // Previously temporarily accepted by a pseudo-FCW, now hard error. |
| 29 | + |
| 30 | + let previous_carve_out_i32 = (42,).0i32; //~ ERROR suffixes on a tuple index are invalid |
| 31 | + let previous_carve_out_i32 = (42,).0u32; //~ ERROR suffixes on a tuple index are invalid |
| 32 | + let previous_carve_out_isize = (42,).0isize; //~ ERROR suffixes on a tuple index are invalid |
| 33 | + let previous_carve_out_usize = (42,).0usize; //~ ERROR suffixes on a tuple index are invalid |
| 34 | + |
| 35 | + // Not part of the carve outs! |
| 36 | + let error_i8 = (42,).0i8; //~ ERROR suffixes on a tuple index are invalid |
| 37 | + let error_u8 = (42,).0u8; //~ ERROR suffixes on a tuple index are invalid |
| 38 | + let error_i16 = (42,).0i16; //~ ERROR suffixes on a tuple index are invalid |
| 39 | + let error_u16 = (42,).0u16; //~ ERROR suffixes on a tuple index are invalid |
| 40 | + let error_i64 = (42,).0i64; //~ ERROR suffixes on a tuple index are invalid |
| 41 | + let error_u64 = (42,).0u64; //~ ERROR suffixes on a tuple index are invalid |
| 42 | + let error_i128 = (42,).0i128; //~ ERROR suffixes on a tuple index are invalid |
| 43 | + let error_u128 = (42,).0u128; //~ ERROR suffixes on a tuple index are invalid |
| 44 | +} |
| 45 | + |
| 46 | +fn numeral_struct_field_name_suffix_invalid() { |
| 47 | + let invalid_struct_name = X { 0suffix: 0, 1: 1, 2: 2 }; |
| 48 | + //~^ ERROR suffixes on a tuple index are invalid |
| 49 | + match invalid_struct_name { |
| 50 | + X { 0suffix: _, .. } => {} |
| 51 | + //~^ ERROR suffixes on a tuple index are invalid |
| 52 | + } |
| 53 | +} |
| 54 | + |
| 55 | +fn numeral_struct_field_name_suffix_previous_carve_out() { |
| 56 | + let carve_out_struct_name = X { 0u32: 0, 1: 1, 2: 2 }; |
| 57 | + //~^ ERROR suffixes on a tuple index are invalid |
| 58 | + match carve_out_struct_name { |
| 59 | + X { 0u32: _, .. } => {} |
| 60 | + //~^ ERROR suffixes on a tuple index are invalid |
| 61 | + } |
| 62 | +} |
| 63 | + |
| 64 | +// Unfortunately, it turns out `std::mem::offset_of!` uses the same expect suffix code path. |
| 65 | +fn offset_of_suffix() { |
| 66 | + #[repr(C)] |
| 67 | + pub struct Struct<T>(u8, T); |
| 68 | + |
| 69 | + // Previous pseudo-FCW carve outs |
| 70 | + assert_eq!(std::mem::offset_of!(Struct<u32>, 0usize), 0); |
| 71 | + //~^ ERROR suffixes on a tuple index are invalid |
| 72 | + |
| 73 | + // Not part of carve outs |
| 74 | + assert_eq!(std::mem::offset_of!(Struct<u32>, 0u8), 0); |
| 75 | + //~^ ERROR suffixes on a tuple index are invalid |
| 76 | +} |
0 commit comments