Why would you learn C++ in 2016?

Re:Why would you learn C++ in 2016? by andrepd on Tuesday April 12, 2016 @10:34PM (#11485294)

There are a few things I disagree, but at least one is factually wrong. C++ is as fast as C, if nothing else because it's (almost) a superset of it.

[ Parent | on HN ]

Re:Why would you learn C++ in 2016? by burfog on Wednesday April 13, 2016 @03:26AM (#11486387)

The things C++ is missing include performance features. It's missing the "restrict" keyword.

https://en.wikipedia.org/wiki/Restrict

Some compilers offer "__restrict" or "__restrict__" in C++, but it's not standard. Standard C++ lacks the feature.

Besides "restrict", there is also the matter of theory not matching practice. The norm for C++ programmers is to be at least somewhat unaware of various extra copies and allocation. You know it's true. In practice, this makes the language slower.

[ Parent | on HN ]

Re:Why would you learn C++ in 2016? by bitbiter on Wednesday April 13, 2016 @01:24PM (#11490217)

C++ has std::valarray that has aliasing rules similar to the restrict keyword, allowing the same types of optimizations.

[ Parent | on HN ]

Re:Why would you learn C++ in 2016? by mhaymo on Wednesday April 13, 2016 @11:06AM (#11488768)

Forgive my ignorance, but doesn't std::unique_ptr communicate the same restriction, and therefore enable the same optimisations?

[ Parent | on HN ]

Re:Why would you learn C++ in 2016? by firethief on Thursday April 14, 2016 @01:13AM (#11494429)

unique_ptr has unique ownership; it's not an error to use other pointers to the same data (just a bad idea).

[ Parent | on HN ]