Porting the Go compiler to Go

Posted Apr 29, 2014 3:56 UTC (Tue) by PaulWay (guest, #45600)
In reply to: Porting the Go compiler to Go by torquay
Parent article: Porting the Go compiler to Go

Heh. If operator overloading is seriously the best feature you can think of for why to use C++ rather than Go, then I don't think you've really made a good case :-)

If you're criticism of Go is that it's not much better than C, and you think C++ is, then really you're just blinding yourself.

Ironically (IMO), Go is at about that level precisely so that it's a familiar transition for C, C++ and Java programmers. If Go is too low level for you, write Python or whatever.

Have fun,

Paul

Porting the Go compiler to Go

Posted Apr 29, 2014 12:05 UTC (Tue) by mpr22 (subscriber, #60784) [Link]

Operator overloading and convenient type-safe generics, together, make a fairly compelling argument for me. If I pick up another statically typed compiled language any time soon, it'll most likely be Rust, which already has both.