The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation but not in the signature. Struct types must now reveal their fields in the signature for the type, though the fields may still be labelled 'private' or 'internal'.
The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was present ...
The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was required ...
The {0} definitions in the signature and implementation are not compatible because the accessibility specified in the signature ...
The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
The {0} definitions in the signature and implementation are not compatible because the field {1} was required by the signature ...
The {0} definitions in the signature and implementation are not compatible because the implementation defines a struct but ...
The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' ...
The {0} definitions in the signature and implementation are not compatible because the implementation is an abstract class ...