Jonathan Müller

You have to detect it manually. Loop over members and check whether member functions, conversion operators and destructors are pure virtual by `is_pure(func.virtual_info())`.

Loop over the parents and handle cpp_namespace.

Yes, it is. They need to be generated on the actual platform you're using.

I know nothing about cross-compling, sorry.

Yeah, that's unfortunate. As a quick workaround, you can heap allocate the pool itself. I'll see what I can do in the library side, but it doesn't look good.

Agree. Dokumentation improvement is on my Todo-List. Also plan to add groups, e.g. all allocator classes, adapters, etc. for easier overview.

> It would also be very helpful, to have an more complex example where we build something like the complex composed allocator Andrei Alexandrescu showed in the video: https://youtu.be/LIb3L4vKZ7U?t=4125 I...

Yes, I plan on implementing that but haven’t thought about the problem yet.

> I did not notice the bitmask op existed thank you. Perhaps this could be added to the integer ops by default, I had expected them to be present there....

I'm not a big fan, as it requires a limit include and isn't such a common functionality.