Calls to super.method() inside a frozen code block are
not semantic exceptions if they are calls to a method
that happens to be in java.lang.Object (e.g. hashCode,
toString etc.). This should be a compile time error always.
might as well fix our naming 'bugs' at the same time.
that is, we use various names for fields in Frozen and for
method calls in Frozen.
we should
* make our names more obscure to reduce risk of clashing
* consider throwing an error when they do clash (user
isn't expected to know about internals of frozen classes, so
shouldn't be using the same names as us)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1045097
might as well fix our naming 'bugs' at the same time.
that is, we use various names for fields in Frozen and for
method calls in Frozen.
we should
* make our names more obscure to reduce risk of clashing
* consider throwing an error when they do clash (user
isn't expected to know about internals of frozen classes, so
shouldn't be using the same names as us)