U-00DC-Sprache

language suitable for developing of complex programs. PanzerMortyr has more than 70000 lines of code, which includes data loading code, game logic, rendering (using OpenGL and a hand-written software rasterizer), audio code, etc. Thanks to Ü design preventing memory safety issues and minimizing other bugs without sacrificing performance I have achieved great performance without spending much time debugging and fixing bugs in such a huge codebase. A video demonstrating actual gameplay and graphics (with software rendering): https://youtu.be/NepOPAPDvwA An article describing some aspects of PanzerMortyr's development in details: https://gist.github.com/Panzerschrek/4e61056f6ce8055ab5fc1d5...

rements. I think it's now ready for a wide audience. Ü is a general-purpose programming language designed to be safe and fast and it achieves these goals. Surprisingly achieving both doesn't require insanely complex language design and compiler implementation. Static typing in combination with clever compile-time analysis and safe/unsafe code separation allow achieving safety. Compilation into machine code (with help of LLVM) provides enough speed. Also Ü just doesn't do much in runtime which could slow-down its performance - most of the safety checks are done in compile-time and destructor-based memory and resources management requires no runtime penalty typical for languages with garbage collection. Ü isn't just a better C with a couple of bells and whistles. It's pretty feature-reach, much like C++ is. These features include classes, inheritance, type and function templates, lambdas, coroutines, compile-time reflection and possibilities of compile-time code generation. Ü uses curly braces-style syntax, but it doesn't try to copy all syntax elements of some particular language. There are keywords and syntax elements borrowed from C++, Rust or whatever else. Despite this most syntax rules should be pretty familiar for users of mainstream programming languages. I have developed and continue developing two compilers for Ü - one written in C++ and another one written in Ü itself (specifically frontends, both use LLVM backend written in C++). Besides that Ü has many other components like its own standard library, a build system, a language server, a tool for C headers conversion, etc. I believe that the language is ready to be used for writing some real code. Having a self-hosted compiler and many other components written in it should prove this claim to be true. Ü maybe isn't ready for very reliable industrial code doing serious stuff (like OS kernels or banking software), but it should be fine to use it for things like hobby projects. See examples (https://github.com/Panzerschrek/U-00DC-Sprache/tree/master/s...) to get a general idea what Ü is and how it looks like and feels. Read the documentation (https://panzerschrek.github.io/U-00DC-Sprache-site/docs/en/c...) for more details. If you have some questions about the specific mechanism providing safety, read the corresponding chapter (https://panzerschrek.github.io/U-00DC-Sprache-site/docs/en/r...). If some topic isn't clear for you after reading the documentation, contact me and I can answer your questions. You may ask, why have I named my language Ü? The answer is simple: I wanted a single-letter name, but all regular Latin letters were already used (https://beza1e1.tuxen.de/one_letter_proglangs.html). So I chose a letter, which belongs to extended Latin alphabet and is pretty common in many natural languages (like German).