Fix bug where a type reference to a nested value type (struct or enum) might not be marked correctly as being a value type. This can happen when the first reference to it does not specify whether or not it is a value type (e.g., if the first reference to it is as the operand to an unbox.any instruction). In that case, the reader creates a type reference that is not marked as a value type. If it ever sees a reference to it that disambiguates it, then it goes back and updates the type reference. But if the copier makes a copy of the reference before it is updated, then the copy will not be marked as being a value type.  There had already been the same check as this commit, but only for namespace type references, not nested type references. (#44)
Fix bug where a type reference to a nested value type (struct or enum) might not be marked correctly as being a value type. This can happen when the first reference to it does not specify whether or not it is a value type (e.g., if the first reference to it is as the operand to an unbox.any instruction). In that case, the reader creates a type reference that is not marked as a value type. If it ever sees a reference to it that disambiguates it, then it goes back and updates the type reference. But if the copier makes a copy of the reference before it is updated, then the copy will not be marked as being a value type.  There had already been the same check as this commit, but only for namespace type references, not nested type references. (#44)


mike-barnett/cci