Vix.cpp v2.1.4

Vix.cpp v2.1.4 is a code quality and build consistency release. This release focuses on making the codebase warning-free under strict compiler flags, improving runtime safety, cleaning CLI internals, standardizing CMake usage across modules, and isolating third-party warnings more effectively. The focus of this release is maintainability. A runtime ecosystem cannot stay reliable if warnings, unsafe patterns, inconsistent CMake usage, and platform-specific code paths accumulate over time.

Warning-free builds

The main improvement in Vix.cpp v2.1.4 is the cleanup required to reach a warning-free build across CLI, core, and modules. The codebase was cleaned under strict compiler flags such as:

-Wall -Wextra -Wconversion

This matters because warnings in a C++ runtime are not just cosmetic. They can hide real bugs, unsafe conversions, unused execution paths, platform assumptions, and future portability issues. Vix.cpp v2.1.4 reduces that risk by treating warning cleanup as part of runtime quality.

Safer runtime code

This release replaces several unsafe or noisy implementation patterns with cleaner modern C++ constructs. That includes reducing unsafe snprintf usage, removing redundant moves, cleaning implicit conversions, and improving request/session construction paths. The goal is not only to silence warnings. The goal is to make the runtime code easier to reason about and safer under stricter compiler analysis.

Core and session fixes

The core module receives fixes around const char[] versus char* handling. This prevents template issues and removes warning noise in console-related code. The session layer also removes redundant std::move usage during request construction. This makes the code cleaner and avoids misleading ownership signals. Small fixes like these matter in a runtime because they improve correctness and readability at the same time.

CLI cleanup

Vix.cpp v2.1.4 cleans several CLI internals. Unused variables, functions, and parameters were removed across commands and the REPL. Platform-specific helpers are now better guarded so Windows-only utilities do not affect other targets. The run command also removes unused runtime variables, and the REPL receives improved argument parsing and validation. This makes the CLI easier to maintain and reduces the chance that unused or platform-specific code creates warnings in unrelated builds.

CMake consistency

This release improves build system consistency across modules. CMake configuration now uses more consistent target_link_libraries patterns, avoiding mixed signature usage and reducing linking inconsistencies. For a modular C++ project, CMake consistency is part of the architecture. If each module expresses dependencies differently, package exports, standalone builds, and umbrella builds become harder to maintain. Vix.cpp v2.1.4 cleans that foundation.

Third-party warning isolation

External warnings from dependencies such as Asio, spdlog, and fmt are now better isolated using SYSTEM includes. This keeps strict warning builds focused on Vix code instead of surfacing warning noise from third-party headers. That distinction is important. Vix should remain strict about its own code, while not letting external dependency warnings break the developer experience.

CLI documentation

The CLI command reference was updated. The README now reflects the complete vix -h command list, giving users a more accurate view of available commands. Documentation consistency matters because CLI behavior and documentation should evolve together.

Developer experience

Vix.cpp v2.1.4 improves the development environment by making builds cleaner, warnings more meaningful, and module behavior more consistent. A warning-free codebase gives contributors a stronger baseline. New warnings become easier to notice because they are not hidden inside existing noise. This directly improves long-term maintainability.

Highlights

  • Cleaned CLI, core, and modules for warning-free builds.
  • Improved strict compiler compatibility with -Wall, -Wextra, and -Wconversion.
  • Standardized CMake configuration across modules.
  • Improved target_link_libraries consistency.
  • Isolated third-party warnings using SYSTEM includes.
  • Improved CLI command handling.
  • Improved REPL flow and validation.
  • Replaced unsafe or noisy runtime patterns with safer C++ constructs.
  • Fixed const char[] versus char* handling in core console code.
  • Removed redundant std::move usage in session request construction.
  • Removed unused CLI variables, functions, and parameters.
  • Guarded platform-specific helpers correctly.
  • Removed unused runtime variables in vix run.
  • Fixed CMake linking inconsistencies.
  • Updated the CLI command reference in the README.

Compatibility

Vix.cpp v2.1.4 introduces no breaking changes. Existing projects remain compatible. The main difference is internal quality: builds should be cleaner, warnings should be reduced, and CMake configuration should be more consistent across modules.

Notes

Vix.cpp v2.1.4 is a maintenance release, but it is strategically important. Warning-free builds, strict compiler hygiene, safer runtime patterns, clean CMake boundaries, and accurate CLI documentation all make the project easier to evolve. This release improves the foundation that later runtime, SDK, and packaging work depends on.