And partly took as long as it did because of need to engage and reconcile with Node use cases as best we could.
-
-
Yeah I get it guys - as I said the TS community is crazy on this one :)
-
Sounds overly fussy given TS only cares about class interfaces rather than class names.
-
It's about name consistency (even after rename) in large code base / teams, don't call same thing Buffer in one file and Blob in another
-
There is still the flexibility to give other name; use 'as', which makes it very clear to reader that you are doing this
-
So let me make sure I'm understanding. The consistency you're looking for is "anywhere I see Blob in a file it means the same thing", but...
-
Since you can use `as` you can't know that *unless you look at the import*. So how is that different from seeing `extend` and seeing ...
-
The diff is being forced to "do it right by default", rather then being forced to think about + needing lint rules to check you did right
- 10 more replies
New conversation -
-
-
The point of default export is "the module name is the name of the object, and you don't need to say it twice"
-
Use list::List pattern in rust sucks so much people (including std) use the facade pattern to avoid it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.