News for hackers. Stuff that matters.

A comment on The ups and downs of porting 50k lines of C++ to Go (2015). Parent comment

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by kccqzy on Thursday March 14, 2019 @04:11AM (#19387314)
Indeed if you actually are using Haskell in production, there's no way your coworkers won't be able to understand a simple signature with three classes. They probably aren't Haskell beginners. Please, have some confidence in your coworkers' intelligence and reasoning ability.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by foldr on Thursday March 14, 2019 @05:41AM (#19387687)
The issue isn't understanding the signature per se. The point is that type signatures aren't always enough to figure out what a function does.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by mruts on Thursday March 14, 2019 @06:40AM (#19388003)
That’s a good point, but often a type signature constrains the possible programs to such a degree that there is only one nonsensical program that can be written with that signature.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by foldr on Thursday March 14, 2019 @06:57AM (#19388081)
That's rarely the case for effectful code, which is where you'd typically see multiple monadic type class constraints.
[ Parent | on HN ]