https://trust-lang.net/en/blog/safety/ Recent content in Software safety on TrustLang Hugo en https://trust-lang.net/en/blog/safety/stack-overflow/ Wed, 07 Jan 2026 00:00:00 +0000 https://trust-lang.net/en/blog/safety/stack-overflow/ <p>January 7 at 14:53 2026</p> <p>Developing the idea of a <a href="https://trust-lang.net/en/blog/safety/language-guarantees/">trusted programming language</a>, 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.</p> <p>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.</p> https://trust-lang.net/en/blog/safety/language-guarantees/ Mon, 10 Nov 2025 00:00:00 +0000 https://trust-lang.net/en/blog/safety/language-guarantees/ <p>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.</p> <p>To reduce the number of errors, many methods were developed, including the creation of specialized source code analysis tools and even entire programming languages.</p> <p>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.</p>