You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just noticed a case that we may not cover — but I did not search very thoroughly, so this issue might be a no-op because we have it already:
We should cover name clashes and name near-clashes with the representation variable of an extension type, because the representation variable is given special treatment in so many ways. Stuff along these lines:
extension typeET1(int id1) {
voidid() {} // No problems with this one, is just redeclared a few times.externalint id2;
}
extension typeET2a(int id) {
voidid() {} // Name clash with representation variable.
}
extension typeET2b(int id) {
setid(_) {} // OK, name is `id=`.
}
extension typeET2c(int id) implementsET1 {
staticint id =1; // Name clash with representation variable.
}
extension typeET2d(int id) implementsET1 {
staticStringget id1 =>''; // Class member conflict with `ET1` representation variable.voidid2() {} // OK, redeclares.
}
The text was updated successfully, but these errors were encountered:
Just noticed a case that we may not cover — but I did not search very thoroughly, so this issue might be a no-op because we have it already:
We should cover name clashes and name near-clashes with the representation variable of an extension type, because the representation variable is given special treatment in so many ways. Stuff along these lines:
The text was updated successfully, but these errors were encountered: