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 whateveracct on Thursday March 14, 2019 @12:55AM (#19386613)
It's just a shame that you could EASILY bolt on basic parametric polymorphism to Go with 0 cost and huge benefit. And it'll never happen.

The power of a universally quantified interface cannot be underestimated!

[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by joeblubaugh on Thursday March 14, 2019 @01:43AM (#19386775)
Never? This is one of the basic proposals in the Go 2 roadmap.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by pjmlp on Thursday March 14, 2019 @02:49PM (#19392231)
Rob Pike is against the current proposal and clearly states it comes from the community.

https://www.youtube.com/watch?v=RIvL2ONhFBI

[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by cgag on Thursday March 14, 2019 @01:54AM (#19386812)
the cost of power is chronically underestimated
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by whateveracct on Thursday March 14, 2019 @03:04AM (#19387058)
Exactly - parametric polymorphism doesn't give you power. It in fact only ever makes your types more constrained!

In a theoretical Go:

    func id<A>(a A) A
This only has one terminating, non-panicking valid implementation.
[ Parent | on HN ]