It's all inhouse code unfortunately, and from a previous life :) What I still do in my open source libraries is to allow overriding the assert macro so that pe

It's all inhouse code unfortunately, and from a previous life :) What I still do in my open source libraries is to allow overriding the assert macro so that people can integrate their own assert implementation (along with allowing to override memory allocation). > Except for writing your own stdlib. How long did that take? Was that to enhance bounds checking? TBH the main reason was that I think the C++ stdlib APIs have terrible ergonomics. We modelled our container classes after C# containers and some common sense. Full control over memory allocation and asserts was just a side effect.