-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export default on interface not allowed #3194
Comments
It's by design. You can accomplish the exact same effect with interface Foo {
// stuff
}
export default Foo; More discussion in #3095. |
I'm OK with leaving it as is if the reasoning is that interfaces, et al, are not vaid EcmaScript and #3917 is implemented. |
hi all, i unexpectedly encountered this too. @ahejlsberg, can you clarify on your remarks further? the discussion in #3095 seems to be focusing more on the declaration collisions, which is all said and good. @clavecoder, i don't fully see the rationale you point to. these remarks are (of course) stated in a cordial tone. however, this decision feels very counterintuitive to me |
Allowing |
oh i see! thanks. i'll follow on over there. |
Raised on SO. The following is an error:
By design or bug?
The text was updated successfully, but these errors were encountered: