Static, Manifest, Evadable, ... But Valuable?

chromatic on 2007-12-31T02:44:44

Strong-typing is a much better way to state intent then relying on the descriptiveness of a property name. Granted, it is possible that this truth is false, but 99% of the time it won't be false, and even then, proper use of unit testing can get us to 100%.

Dan Allen, Generics are the best we've ever had

It is possible that a property name can be truly descriptive (and in maintainable code 99% of the time it won't be), and proper use of unit testing can get us to 100%.

Faint praise for busywork (and come on, anyone who uses the phrase "strong typing" in all seriousness as if it actually meant something other than "You're going to wear out your keyboard and wrists soon!" inspires little confidence) doesn't impress me much. Type erasure less so.


Let the programmer decide?

spen on 2008-01-04T22:11:09

Will Perl 6 let the programmer decide when to use strong typing? I can see where it is sometimes useful, but sometimes a pain.

Re:Let the programmer decide?

chromatic on 2008-01-05T00:24:09

Perl 6 allows optional typing. If you want to put types in your function and method signatures, you can. This may even be a good idea in some cases.

The compiler (and runtime when appropriate) will check types for you.