Jeremy Rifkin

Awesome thanks! Is `set(assert_DIR ${VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/share/libassert)` still needed? One way or another, I'm reworking the cmake to use `libassert` internally not `assert` for the reasons @Cazadorro pointed out :)

This is now resolved as as soon as https://github.com/microsoft/vcpkg/pull/37506 is merged

Thanks for opening this issue! I'd definitely like to support contracts. `[[pre: ASSERT(num > 0)]]` would be required for getting the value of `num` and it should be possible to...

This is unfortunate, there's another issue I remember with shenanigans relating to library functions. This is definitely difficult to handle without more comprehensive parsing.

The reason it's called "Conformance View" is that it's designed for checking conformance in relation to how different compilers and different versions conform to the standard, how different compilers and...

We are now hosting msvc compilers and execution is restored 🎉

Awesome!

I believe this is library code filtering. With -g0 our asm parser doesn’t know what is library code and what is not, disabling library filtering in the compiler without -g0...

Thanks for the report, that looks like a bug. Partouf will be the expert but it looks like an issue with what debug symbols gcc is emitting: -O0 ```x86asm function::~function()...

Thank you for reviewing, I've updated to address the review comments