3 ms·
It sounds like type inference for object literals is coming along, even if there a few quibbles about some of the defaults on literals mentioned here. Did they
by Roboprog 7y ago
It sounds like type inference for object literals is coming along, even if there a few quibbles about some of the defaults on literals mentioned here.
Did they ever get a solution in place for partial function application (e.g. - as for Ramda.js)?
When this gets to the point where the only place I have to define explicit types is for JSON data read from the network, I’ll consider using it.
I know I’m in the minority, but I’d rather NOT have any type checking than have to read through Java-esque drivel (at least most modern languages put the types after the identifier like Pascal does, rather than before like C). In practice, I don’t spend much time chasing type errors, but do spend too much time reading through MEGO inducing verbiage which I would just as soon not.
- jasonhansel 7y agoI think it's best to require type annotations at interface boundaries, but not within implementations. That way, changes to the interface are obvious, but excessive verbosity within a module is limited.