Someone broke boost and modules, at least I managed to make a workaround but come on

Don't worry. If a library from boost gets included in std it will be broken for decades. Gotta protect that abi.

@Demolishun Ah yes the holy ABI, I can't understand why they don't just say with C++ 26 (or whatever version X amount of years in the future) that they will be replacing it with a better managed system that may make available with an earlier version.

Hell the std module would have been a perfect time for it “if you use modules then you work with the new abi system”

I don't even want boost, but it seems the most recommended C++ redis library got absorbed

@BordedDev I think the ABI from maybe even further back than XP is compatible with ABI of now on Windows. Not sure though. Some of this is vendor driven. I dunno. I get there is a compatibility issue there, but I haven't got a good mental model for it.

@BordedDev I don't get why its such an issue. I think for the most part you don't share C++ objects across interfaces like in DLLs and SOs. But maybe I just don't know and am talking out my ass. I had read that its safest to only share really simple objects across interfaces.

@Demolishun Honestly I'm not too sure either, I assume the addresses in the DLLs just can't change since then it will try to execute the wrong code

@BordedDev like if you transfer a vector across a dll interface. The internal representation can't change. That is what I was thinking.