What was the ISO C++ committee rationale to not accept intrusive pointers and containers to any current C++ standards?

247 views Asked by At

It seems that every single high performance and low latency platform I work with use intrusive pointers and containers to manage the lifetime cycle of their objects. Game engines, trading systems, avionics and others.

Intrusive pointers have been available from boost for more than 20 years and intrusive/flat containers are widely available as well (eg google dense hash map).

If C++ is a performance-oriented language, what is the current rationale for the ISO C++ committee to stall or reject all intrusive pointers and containers proposals into a C++ standard even though they are one of the most widely used tools to achieve very low latency?

0

There are 0 answers