Making Your Own Container Compatible with C++20 Ranges

Re:Making Your Own Container Compatible with C++20 Ranges by monocasa on Monday March 22, 2021 @07:56PM (#26549159)

This kind of thing is easily one of my favorite pieces of C++. I used to be the OS lead for a proprietary C++14 RTOS, and being able to build our own intrusive collections libraries that were able to use all the same syntax sugar as the STL was absolutely killer.

IMO, all systems languages should be expressive enough to implement their standard libraries and containers as normal language code, but sadly that isn't always the case.

[ Parent | on HN ]

Re:Making Your Own Container Compatible with C++20 Ranges by slavik81 on Monday March 22, 2021 @08:14PM (#26549296)

> One of my fundamental aims for C++ is (from the very start in 1979) to provide equally good support for user-defined and built-in types. For example, I’d like to be able to build an integer type that is as good as the built-in int in every way (with the possible exception of compile time).

~ Bjarne Stroustrup, How can you be so certain? (2019)

[ Parent | on HN ]

Re:Making Your Own Container Compatible with C++20 Ranges by pjmlp on Tuesday March 23, 2021 @03:05AM (#26551929)

Which made me an early adopter in 1993 for MS-DOS, as C already felt primitive back then.

However I still dream of the day where static analysis can fix all possible security issues.

[ Parent | on HN ]

Re:Making Your Own Container Compatible with C++20 Ranges by nicoburns on Tuesday March 23, 2021 @05:59AM (#26553056)

Which systems languages can't do this?

[ Parent | on HN ]

Re:Making Your Own Container Compatible with C++20 Ranges by rfoo on Wednesday March 24, 2021 @03:40AM (#26564507)

The only one I'm aware of is Golang.

[ Parent | on HN ]