Closed MichalStrehovsky closed 2 years ago
To repro, add a new field of some otherwise not kept type and e.g. assign a null to it in Main.
Main
In the FieldDefinitionNode we currently just copy the signature blob over, which means we don't analyze/rewrite what the field type refers to. The fix will look similar to https://github.com/MichalStrehovsky/iltrim/pull/33/commits/f632a122539cb89166a4f13761639d8272c7772b, except field signatures are simpler (there's just one type).
Please hook up MemberReference too, same as in the above commit (you can test it by e.g. reading the String.Empty field in Main).
String.Empty
For reference, field signatures are described in II.23.2.4 FieldSig of the ECMA-335 spec.
To repro, add a new field of some otherwise not kept type and e.g. assign a null to it in
Main.In the FieldDefinitionNode we currently just copy the signature blob over, which means we don't analyze/rewrite what the field type refers to. The fix will look similar to https://github.com/MichalStrehovsky/iltrim/pull/33/commits/f632a122539cb89166a4f13761639d8272c7772b, except field signatures are simpler (there's just one type).
Please hook up MemberReference too, same as in the above commit (you can test it by e.g. reading the
String.Emptyfield in Main).For reference, field signatures are described in II.23.2.4 FieldSig of the ECMA-335 spec.