Verification on TrustLang

Guarantees and safety

Mon, 01 Jan 0001 00:00:00 +0000

This section brings together the TrustLang capabilities that are responsible for the safety and quality of programs: safe memory management, protection from data races, correctness control at compile time and formal verification.

Each capability is described in detail in exactly one place (the source page) and is only mentioned here with a summary and a link. Detailed lists of options/diagnostics are not duplicated — their source is the tool’s help (trust --help, trust -Whelp, LSP hovers).

Status and plans

Mon, 01 Jan 0001 00:00:00 +0000

Implemented in the current version (0.6.0)

The syntax concept has been developed
The macro syntax has been defined
Parser and literals for basic data types
The concept of language guarantees has been formulated
The playground for testing examples has been developed

Getting rid of Segmentation fault errors due to stack overflow in C++

Wed, 07 Jan 2026 00:00:00 +0000

January 7 at 14:53 2026

Developing the idea of a trusted programming language, I came to the conclusion that, through restrictions of the syntax and the creation of corresponding checks in the static code analyzer, it is possible to protect against practically all technical errors except two — the control of dynamically allocated memory and stack overflow.

Moreover, while solutions exist for reference counting at runtime, stack overflow control cannot be done not only during the analysis of the source text of the program, but it is practically impossible even during the execution of the application! After all, a stack overflow error is always fatal, since there is no way to catch and handle this error from inside the running program in order to then continue its execution as if nothing had happened.

Programming language guarantees as a basis for secure software development

Mon, 10 Nov 2025 00:00:00 +0000

Errors in composing programs for computers appeared even earlier than the very first programming languages were invented. Actually, programming languages were invented precisely so that programs would be written more simply, and the number of errors in them would be as small as possible.

To reduce the number of errors, many methods were developed, including the creation of specialized source code analysis tools and even entire programming languages.

But after many decades, the problem of purely technical errors in software still remains unsolved to this day, however the approach proposed in the Rust language changes everything.