9 Oct
2017
9 Oct
'17
9:37 a.m.
Hans Dembinski wrote:
This is kinda sad, because the library is much less useful if tagged_ptr is not guaranteed to work on all platforms now and in the future. Just assume you use this in a large project and rely on it, and then a new processor generation comes out where tagged_ptr does not work anymore. That being said it is probably still useful for special projects, but not something to put in Boost. :(
On the contrary, this is exactly why it needs to be put in Boost - to isolate the platform-specific differences behind a portable interface.
but smart people on Reddit showed me that I am relying on undefined behaviour here.
Out of curiosity, what's the specific problem that was pointed out? What behavior is undefined?