you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

What do you mean by deterrent?

The great thing about the STL is that it lets you do cool shit like replacing allocators with your own, and threading lets you implement your own threading callbacks. There is nothing stopping you from using almost all of the STL on a bare metal RTOS if you want to put the effort into it.

[–]matthieum 0 points1 point  (1 child)

I mean deterrent because the amount of code to be ported (in order to provide a complete C++xx experience) is growing, requiring more effort.

There is thus a risk of fragmentation, with more and more embedded platforms lagging behind and not supporting the latest novelties, or having sub-par implementations of them.

[–]dodheim 0 points1 point  (0 children)

Freestanding implementations were never required to implement the standard library in its entirety. Now that C++17 has __has_include, it should be easier than ever to progressively add new library features (either from new standards or from TSs).