Open jamiebullock opened 1 year ago
OK, the reason for this is that RogueVector
relies on internal implementation details of std::vector
, and these have now changed in the latest Microsoft C++ Standard Library.
So rather than std::vector::_Mylast
we now have (for example) std::vector::_Mypair._Myval2._Mylast
where _Mypair
is private.
I don't see any way around this besides rewriting RogueVector
so that it no longer inherits std::vector
(something that should arguably done anyway). It should use a non-owning data structure such as std::span.
I'm trying to compile "natively" on Windows 64-bit.
Currently using:
The build fails with many instances of:
Anyone know how to get around this?