Fix: Instance vars should not be allowed on Class
, Tuple
, NamedTuple
, Enum
, Pointer
, Proc
, StaticArray
and Union
.
#12160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #12159.
The compiler now produce an error when user define an ivar on these types:
Class
,Tuple
,NamedTuple
,Enum
,Pointer
,Proc
,StaticArray
andUnion
.(similar to previously triggered errors on forbidden types
Int32
Number
,Object
...)Note that
TupleInstanceType
orNamedTupleInstanceType
still inherit from moduleInstanceVarContainer
throughGenericClassInstanceType
, but couldn't touch that becauseGenericClassInstanceType
is used by every generic class.