extension type ET3(i);I think these both should be OK. I put these here based on a thread of comments with @eer...@google.com in https://dart-review.googlesource.com/c/sdk/+/457502/comment/a9fca80c_315a1633/
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
extension type ET3(i);I think these both should be OK. I put these here based on a thread of comments with @eer...@google.com in https://dart-review.googlesource.com/c/sdk/+/457502/comment/a9fca80c_315a1633/
Yes, the missing `final` is inferred when the declaration is an extension type.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
extension type ET3(i);Erik ErnstI think these both should be OK. I put these here based on a thread of comments with @eer...@google.com in https://dart-review.googlesource.com/c/sdk/+/457502/comment/a9fca80c_315a1633/
Yes, the missing `final` is inferred when the declaration is an extension type.
Shouldn't `extension type ET3(i);` be an error since there is explicit type?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
(Another drive-by comment added)
extension type ET3(i);Erik ErnstI think these both should be OK. I put these here based on a thread of comments with @eer...@google.com in https://dart-review.googlesource.com/c/sdk/+/457502/comment/a9fca80c_315a1633/
Johnni WintherYes, the missing `final` is inferred when the declaration is an extension type.
Shouldn't `extension type ET3(i);` be an error since there is explicit type?
Again, using the general rules about formal parameter lists as part of the adoption of primary constructor syntax for extension types rather than special casing it, the type annotation can be omitted. So `ET3(i)` should be OK.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |