News for hackers. Stuff that matters.
Re:The Ergonomics of Type Checking (2016) by zpr on Saturday October 28, 2017 @02:39PM (#15576182)
Hate to be that guy but, Flow for JS is something like that. You can optionally enable it and even enable/disable it in certain files, functions, lines, etc.
Re:The Ergonomics of Type Checking (2016) by tuxracer on Saturday October 28, 2017 @10:03PM (#15577662)
The author's ideal language seems to also describe TypeScript https://eng.lyft.com/typescript-at-lyft-64f0702346ea
Re:The Ergonomics of Type Checking (2016) by hliyan on Saturday October 28, 2017 @02:53PM (#15576260)
That is optional typing. The author is talking about gradual or progressive typing.
Re:The Ergonomics of Type Checking (2016) by zpr on Saturday October 28, 2017 @02:58PM (#15576277)
But he mentions he wishes he could start dynamically and end statically. By enabling Flow at the end, don't you basically achieve that? You can also enable it progressively for files as you move on, and still rapidly prototype without it. In fact, unless I'm mistaken I believe it's "opt-in" by default, ie. Flow won't scan the file unless you include the special comment keyword at the top of the file.
Re:The Ergonomics of Type Checking (2016) by mercer on Sunday October 29, 2017 @08:45AM (#15579095)
Could you explain the difference? I though TypeScript was a good example of gradual typing.