less strict ambiguity errors for fields? #3363
Labels
enhancement
New feature or request
front end
related to the front end until .fum file is created: call and type resolution, type checking, etc.
question
A decision or information is required
currently this yields an ambiguity error:
but maybe this is too inconvenient and the field in the current outer or even closest outer should be picked.
Otherwise one would have to specify
my_feat.this.x + 3
orex.this.x + 3
The text was updated successfully, but these errors were encountered: