Luke Scott

How does Razor or Wooting do their implementation? For anyone looking to use this feature, they are going to be looking to match one of those two. So which ever...

@tzarc I'm sorry, but how is my comment off-topic? You asked about which implementation to go with. The implementation people care about is the one that matches what already exists....

Could you simply make trailing types optional, while making leading types required? It would fully depend on how the types were ordered, but I see that as a feature rather...

@ohjames I do see omitting trailing types mentioned in #10571, but it looks like it advocates for an `auto` keyword, which would open the door to `foo()`. Later comments in...

@ohjames > Maybe it is lacking a bit of focus. If there isn't an issue for simply omitting trailing types then maybe someone should open one. That was my thinking...

@ohjames I think what you're saying is: ```typescript function totoro(a: A, b: B): [A,B] { return [a,b] } const result1 = totoro('friend', new Date(2018, 3, 19)) const result2 = totoro('friend',...

Sorry, I just noticed this sifting thru my notifications. Interestingly, I also have these two in my config, so I didn't notice as I use a mix of libraries that...

Ah, so it was an implementation issue. Looks like even in the early version of the standard, 'as default' is considered the same thing. I think where I got confused,...

> I was not using typescript, but used signature_pad like this: `window.SignaturePad = require('signature_pad').default;` > > Changing it to this removed the errror: `window.SignaturePad = require('signature_pad');` > > (this might...