Re:Towards Scala 3
by naasking on Friday April 20, 2018 @02:07PM
(#16887063)
Is that option documented somewhere? I imagine there are some tradeoffs with enabling it.
[ Parent
| on HN ]
Re:Towards Scala 3
by ItsMe000001 on Friday April 20, 2018 @02:14PM
(#16887139)
https://www.typescriptlang.org/docs/handbook/release-notes/t...
> TypeScript 2.6 introduces a new strict checking flag, --strictFunctionTypes.
> The --strictFunctionTypes switch is part of the --strict family of switches, meaning that it defaults to on in --strict mode.
> Under --strictFunctionTypes function type parameter positions are checked contravariantly instead of bivariantly.
> ...(etc.)
Contravariance then, right. Thanks! I haven't gotten into Typescript yet, and at this point it looks fairly large and a little daunting, so this is helpful.
And this project is super interesting: https://1c.wizawu.com/#/whatis Use TypeScript on JVM with both NPM and Maven dependencies
Re:Towards Scala 3
by coryfklein on Friday April 20, 2018 @05:08PM
(#16888446)
The major tradeoff, IMO, is that it is even toggle-able at all, let alone being a feature switch that is enabled by default.
If you enter any random TS project today, odds are it isn't using that switch, and enabling the switch will lead you down a month long rabbit-hole of fixing cascading type errors.
Not only that, but since it isn't required many libraries in the ecosystem won't be using it. Comparing my experiences with TypeScript and Flow vs. my experiences with Haskell, any optional type system is going to leave a lot of gaps if you don't have a pretty strict not-invented-here culture.