Currently, DISSCO produces compiler warnings when building from source on Windows, Linux, and macOS. Although builds and installation can still succeed, these warnings make the output harder to interpret and can obscure genuine problems.
The warning types and volume vary by platform and compiler. They include potentially uninitialized values, numeric conversions, signedness mismatches, unused or shadowed variables, deprecated APIs, and platform-specific pointer truncation.
Windows builds also enable MSVC /Wall, which contributes substantial optimization and library diagnostic noise. However, this is not solely a Windows build-configuration issue: actionable source-level warnings need to be addressed across all three platforms.
Expected behavior
Warning-free builds on Windows, Linux, and macOS, with existing functionality preserved and CI checks to prevent warning regressions.
Currently, DISSCO produces compiler warnings when building from source on Windows, Linux, and macOS. Although builds and installation can still succeed, these warnings make the output harder to interpret and can obscure genuine problems.
The warning types and volume vary by platform and compiler. They include potentially uninitialized values, numeric conversions, signedness mismatches, unused or shadowed variables, deprecated APIs, and platform-specific pointer truncation.
Windows builds also enable MSVC
/Wall, which contributes substantial optimization and library diagnostic noise. However, this is not solely a Windows build-configuration issue: actionable source-level warnings need to be addressed across all three platforms.Expected behavior
Warning-free builds on Windows, Linux, and macOS, with existing functionality preserved and CI checks to prevent warning regressions.