News for hackers. Stuff that matters.
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by Retra on Wednesday November 19, 2014 @06:03PM (#8633268)
This makes me wonder what the point of writing 'var' is if it doesn't tell you the type of the variable.
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by UberMouse on Wednesday November 19, 2014 @08:02PM (#8633802)
So variables are explicitly declared, don't have issues of mis typing a variable name and accidentally declaring a new one.

Note: This is just my thinking, I don't know if it's the actual reason

Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by Retra on Thursday November 20, 2014 @03:20PM (#8637905)
That's a sensible reason, sure, but I'd rather declare it with an actual type instead.
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by thomasahle on Thursday November 20, 2014 @12:06PM (#8636744)
Yes, for complicated things like this, explicitly declaring the type is probably preferable.
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by tomp on Thursday November 20, 2014 @04:32AM (#8634979)
As opposed to doing what?
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by thomasahle on Thursday November 20, 2014 @12:04PM (#8636732)
Like python, just `e = equal(...`
Re:TypeScript 1.4 sneak peek: union types, type guards, and ... by tomp on Thursday November 20, 2014 @12:24PM (#8636851)
Python had to go through a lot of pain for that, the "nonlocal" keyword was only added in Python 3.0, and the local/global distinction is very fragile.

Javascript and Coffeescript try to solve this in different ways, most people think that JavaScript's method sucks, and many are not fond of CoffeeScript's non-locality. Personally, I think that demanding variable declaration is still the best option (possibly except for interactive sessions).