U-00DC-Sprache

KO | EN

gitlite — search

#python #react #android #machine-learning #linux #docker #java #cli #awesome-list #vue #security #ios #mcp #openai

(★ 114)

"Ü" programming language

File Explorer

Download Latest Version (.zip)

- - code_coverage.yml
  - freebsd.yml
  - gnu_linux_aarch64_release_llvm_src.yml
  - gnu_linux_release_llvm_src.yml
  - interpreter_emscripten.yml
  - macos.yml
  - main.yml
  - manual_debug_build_check.yml
  - visual_studio_extension.yml
  - windows.yml
  - windows_advanced.yml
- build_emscripten_llvm_src.sh
- build_freebsd_x86_64_release_llvm_src.sh
- build_gnu_linux_aarch64_release_llvm_src.sh
- build_gnu_linux_x86_64_debug_llvm_src.sh
- build_gnu_linux_x86_64_release_llvm_bin.sh
- build_gnu_linux_x86_64_release_llvm_src.sh
- build_gnu_linux_x86_release_llvm_src.sh
- build_macos_aarch_64_release_llvm_src.sh
- build_visual_studio_extension_windows_x86_64.bat
- build_windows_x86_64_debug_llvm_src.ps1
- build_windows_x86_64_release_llvm_src.ps1
- build_windows_x86_release_llvm_src.ps1
- calculate_code_coverage_gnu_linux_x86_64_debug_llvm_bin.sh
- - build.u
  - CMakeLists.txt
  - README.md
- - async_calls_inlining.cpp
  - async_calls_inlining.hpp
  - CMakeLists.txt
  - code_builder_errors.cpp
  - code_builder_errors.hpp
  - interpreter.cpp
  - interpreter.hpp
  - long_stable_hash.cpp
  - long_stable_hash.hpp
  - mangling.hpp
  - pop_llvm_warnings.hpp
  - push_disable_llvm_warnings.hpp
  - return_value_optimization.cpp
  - return_value_optimization.hpp
  - small_types.hpp
- - CMakeLists.txt
- - build.u
  - CMakeLists.txt
- - CMakeLists.txt
  - code_builder_launcher.hpp
  - linker.cpp
  - linker.hpp
  - linker_coff.cpp
  - linker_elf_freebsd.cpp
  - linker_elf_linux.cpp
  - linker_macho.cpp
  - linker_mingw.cpp
  - linker_stub.cpp
  - main.cpp
  - make_dep_file.cpp
  - make_dep_file.hpp
  - README.md
- - CMakeLists.txt
  - compiler_builtins.cpp
  - compiler_builtins.hpp
  - div_builtins.cpp
  - div_builtins.hpp
  - errors_print.cpp
  - errors_print.hpp
  - prelude.cpp
  - prelude.hpp
  - vfs.cpp
  - vfs.hpp
- - CMakeLists.txt
  - main.cpp
  - README.md
  - u_ast_builder.cpp
  - u_ast_builder.hpp
- - CMakeLists.txt
  - conf_common.py
  - favicon.ico
  - logo-Gebrochene-Grotesk.png
  - README.md
  - sprache_lexer.py
- - async_functions.u
  - classes.u
  - CMakeLists.txt
  - constexpr.u
  - control_flow.u
  - destructors.u
  - enums.u
  - fibonacci_generator.u
  - fibonacci_iterative.u
  - fibonacci_recursive.u
  - function_pointers.u
  - function_templates.u
  - functions_overloading.u
  - hello_world.u
  - http_server.u
  - lambdas.u
  - mixins.u
  - namespaces.u
  - operators_overloaidng.u
  - quine.u
  - quine_embed.u
  - README.md
  - references.u
  - sierpinski_carpet.u
  - sierpinski_triangle.u
  - string.u
  - structs.u
  - type_templates.u
  - udp_socket.u
  - unsafe.u
  - vector.u
  - virtual_methods.u
- - CMakeLists.txt
  - README.md
- - CMakeLists.txt
  - main.cpp
  - README.md
- - async_server.cpp
  - async_server.hpp
  - build_system_integration.cpp
  - build_system_integration.hpp
  - CMakeLists.txt
  - completion.cpp
  - completion.hpp
  - data_layout_stub.cpp
  - data_layout_stub.hpp
  - diagnostics.cpp
  - diagnostics.hpp
  - document.cpp
  - document.hpp
  - document_manager.cpp
  - document_manager.hpp
  - document_position.cpp
  - document_position.hpp
  - document_position_utils.cpp
  - document_position_utils.hpp
  - document_symbols.cpp
  - document_symbols.hpp
  - json.hpp
  - logger.hpp
  - message_queue.cpp
  - message_queue.hpp
  - messages.hpp
  - options.hpp
  - README.md
  - server_handler.cpp
  - server_handler.hpp
  - server_processor.cpp
  - server_processor.hpp
  - syntax_tree_lookup.cpp
  - syntax_tree_lookup.hpp
  - text_change.cpp
  - text_change.hpp
  - transport.cpp
  - transport.hpp
  - uri.cpp
  - uri.hpp
  - vfs_manager.cpp
  - vfs_manager.hpp
- - assert.hpp
  - CMakeLists.txt
  - lex_synt_error.cpp
  - lex_synt_error.hpp
  - size_assert.hpp
  - src_loc.cpp
  - src_loc.hpp
- - editor_widget.cpp
  - editor_widget.hpp
  - plugin.cpp
  - plugin.hpp
  - README.md
  - USprache.json.in
  - usprache.pro
- - CMakeLists.txt
  - sprache_version.cpp
  - sprache_version.hpp
  - UpdateGitRevision.cmake
- - filetypes.U-00DC-Sprache.conf
  - README.md
  - u_kde_syntax_highlighting.xml
  - u_nano_syntax_highlighting
  - u_notepad_plus_plus_syntax_highlighting.xml
- - CMakeLists.txt
  - dummy.cpp
  - execution_engine.hpp
  - py_tests_common.hpp
  - tests_common.hpp
- - CMakeLists.txt
  - README.md
- - .gitignore
  - build.bat
  - FileAndContentTypeDefinitions.cs
  - LanguageClient.cs
  - LanguageServerSettingsModel.cs
  - LanguageServerSettingsPage.cs
  - README.md
  - source.extension.vsixmanifest
  - Ü_extension.csproj
  - Ü_extension.sln
  - Ü_extension_extra.pkgdef
  - Ü_extensionPackage.cs
  - Ü_extensionPackage.vsct
- annotated_tests_run.py
- bin2c.cmake
- CMakeLists.txt
- errors_list.hpp
- keywords_list.txt
.gitattributes
.gitignore
LICENSE
README.md
Ü design principles.md
Ü-Sprache todo list.txt

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

![](https://raw.githubusercontent.com/Panzerschrek/U-00DC-Sprache/master/source/docs/logo-Gebrochene-Grotesk.png)

## The Ü programming language

Ü is a statically-typed compiled programming language, designed for writing programs, which should be both reliable and fast.
It has safe and unsafe code separation, compile-time correctness checks, powerful abstractions like RAII and templates, encapsulation, rich type system, lambdas, coroutines and many other useful features.
Ü uses RAII for memory and resources management (no GC is involved), but manual memory management may be still used in unsafe code.
Ü is memory-safe and race-condition-safe, as long as no unsafe code is involved at all or as long as unsafe code is correctly written.

Ü is heavily inspired by C++, but doesn't have its downsides.
Also it was influenced by Rust, but only slightly and thus is way easier to use in comparison to Rust.
Any possible coincidence with design and features of other programming languages is unintentional.

Ü compiler is based on LLVM library and thus leverages many its powers, including numerous optimizations and code generation support for many CPU architectures and operating systems.
Even more, there are two Ü compilers, the first one is written in C++ and the second one is mostly written in Ü itself (frontend part, backend is still LLVM).

Besides the compiler Ü has a lot of other components.
Ü provides its own standard library containing basic container classes, helpers and operating system interaction functionality.
There is a build system, which simplifies complex Ü programs building and (partially) package management.
For better development experience there is a language server and variety of syntax highlighting files for some IDEs and text editors.
Last but not least, Ü has a tool for C headers conversion, which allows to simplify interaction with foreign code.

### Supported systems

The table below lists supported operating systems and architectures for Ü compiler hosting and targeting.

| Operating system | Architecture | Hosting Ü compiler | Targeting | Notes                                                                              |
|------------------|--------------|--------------------|-----------|------------------------------------------------------------------------------------|
| Windows          | x86          |  +                 | +         | MSVC installation may be necessary.                                                |
| Windows          | x86_64       |  +                 | +         | MSVC installation may be necessary. Supports also running Ü compiler built for x86.|
| GNU/Linux        | x86          |  +                 | +         | 32-bit C libraries installation may be necessary.                                  |
| GNU/Linux        | x86_64       |  +                 | +         |                                                                                    |
| GNU/Linux        | AArch64      |  +                 | +         |                                                                                    |
| FreeBSD          | x86_64       |  +                 | +         |                                                                                    |
| OS X             | AArch64      |  +                 | ±         | Still experimental, some standard library functionality may not work properly.     |

CPU architectures besides x86, x86_64 and AArch64 aren't tested, but they may work if Ü compiler is built with these architecture support (see *LLVM_TARGETS_TO_BUILD* option).
GNU/Linux with x32 ABI isn't supported due to some bugs in LLVM library.

### Documentation

Documentation is available here: [english](https://panzerschrek.github.io/U-00DC-Sprache-site/docs/en/contents.html), [russian](https://panzerschrek.github.io/U-00DC-Sprache-site/docs/ru/contents.html).
The language itself is described in details, other components have basic, but not very deep documentation.
Additionally there are some basic usage [examples](source/examples/README.md).

### Why choosing Ü?

The short answer is: Ü is superior in comparison to many other programming languages in terms of safety, reliability, expressiveness and feature availability.
The table below compares important features, advantages and disadvantages of various programming languages, including Ü.
It lists only languages, which may be directly compared to Ü - statically-typed compiled languages without heavy runtime and/or GC.

| Feature/Language                                                                                 | C  | C++ | Swift | Zig | Odin | Rust | Ü |
|--------------------------------------------------------------------------------------------------|----|-----|-------|-----|------|------|---|
| constructors (special methods for construction, not just factory methods with user-defined name) | -  | +   | +     | -   | -    | -    | + |
| destructors (special methods called automatically at object destruction)                         | -  | +   | +     | -   | -    | +    | + |
| encapsulation (possibility to restrict access to some items only from some scopes)               | -  | +   | +     | +   | +    | +    | + |
| memory-safety (no out-of bounds read/writes, no use-after-free errors, etc.)                     | -  | -   | +⁶    | -   | -    | +    | + |
| thread-safety (no race conditions)                                                               | -  | -   | -     | -   | -    | +    | + |
| type templates                                                                                   | -  | +   | +     | +   | +    | +    | + |
| function templates                                                                               | -  | +   | +     | +   | +    | +    | + |
| duck-typing in templates (without mandatory template type requirements specification)            | -  | +⁴  | -     | +   | +    | -    | + |
| references (with auto reference creation and dereferencing)                                      | -  | +   | -⁷    | -   | -    | -¹⁵  | + |
| functions overloading                                                                            | -  | +   | +     | -   | +¹¹  | -    | + |
| operators overloading                                                                            | -  | +   | +     | -   | -    | +    | + |
| frictionless copying (ability to take deep copy of a value via operator `=`)                     | -¹ | +   | +     | -⁹  | -¹²  | -¹⁶  | + |
| compile-time calculations                                                                        | -² | +   | -     | +   | +    | +    | + |
| compile-time type information                                                                    | -  | -   | -     | +   | -    | -    | + |
| class inheritance and runtime polymorphism based on it                                           | -  | +   | +     | -   | -¹³  | -    | + |
| no exceptions (means no possibility to implicitly skip control flow passing)                     | +³ | -   | +⁸    | +   | +    | ±¹⁷  | + |
| async functions                                                                                  | -  | +⁵  | +     | ±¹⁰ | -    | +    | + |
| lambdas (anonymous functions defined within expression context, sometimes named closures)        | -  | +   | +     | -   | -¹⁴  | +    | + |

<details>
<summary>footnotes</summary>

1 - structs may be copied via `=`, but it's only a shallow copy. 
2 - there is only limited compile-time evaluation of constants like `1 + 2`, but without compile-time variable constants and compile-time functions evaluation. 
3 - `setjump`/`longjump` is still possible, but generally speaking it's not a language feature and it may be implemented almost in any language. 
4 - in some rare cases `typename` keyword is needed in templates. There are also concepts in newer C++ standards, but one can just avoid using them if duck-typing is needed. 
5 - C++ has somewhat lower-level coroutines, which allow implementing not only async functions, but generators and other constructions. 
6 - memory safety was added in new versions of the language. 
7 - there are generally no references, there are `inout` function parameters, but they require specifying `&` for parameter passing. 
8 - Swift has `throw` keyword, `throws` function specifier and `catch` statement, but there is no unexpected control flow, since each possible error value must be explicitly handled or passed further. So, what it does is more like a second function return channel rather than proper exceptions. 
9 - operator `=` only creates shallow copy, just like in C. 
10 - async functions are now in development. 
11 - overloading is explicit and requires adding extra code. 
12 - operator `=` only creates shallow copy, just like in C. 
13 - there is subtype polymorphism, but no proper inheritance-based polymorphism with runtime dispatching based on actual runtime type (via virtual functions or something similar). 
14 - there are only non-capturing functions defined within other functions. 
15 - Rust so-called "references" are really just pointers, one need to add `&` to create a reference and use `*` for dereferencing. 
16 - all types are split into two categories, the first one allows copying via `=` (which is basically `memcpy`), the second one requires explicitly calling `clone` method. 
17 - exceptions can't be thrown within Rust code, but Rust supports stack unwinding (with destructors calling) if an exception is thrown from foreign code (like C++). Code should be written with unwinding possibility in mind.

</details>

As it can be seen, only Ü has both strong safety/reliability guarantees and many necessary and easy to use features and abstractions.
Other languages are unsafe and/or have some important for effective programming features missing.

### How to build

A modern C++ compiler (clang, GCC, MSVC) is required for building the project.
CMake and Ninja are also necessary.

#### Option 0 - build with LLVM sources
* Download LLVM sources [here](https://github.com/llvm/llvm-project/releases/) (version 17.0.6 is used in this project).
* Run cmake for *source/CMakeLists.txt* file to generate a project for your favorite IDE or build system. You must set *LLVM_SRC_DIR* in cmake arguments.
* In order to speed-up the build you may disable building of unnecessary targets via *LLVM_TARGETS_TO_BUILD* cmake variable. For example set it to *X86* only.
* It's recommended to disable LLVM tests and benchmarks. See LLVM documentation for more information.
* Perform the build.

#### Option 1 - build with LLVM binary libraries
* Install proper version of LLVM libraries via your system package manager or download it manually [here](https://github.com/llvm/llvm-project/releases/).
* Run cmake for *source/CMakeLists.txt* file with *LLVM_LIB_DIR* cmake variable specified.
* Perform the build.

Some components are optional and may be disabled via cmake options (see *source/CMakeLists.txt*).
Python 3 is required to build and run tests written in Python.
Sphynx is required to build documentation.
For more information/examples see build scripts in the *ci* directory.

### Component readmes

[compiler](source/compilers_common_lib/README.md)

[language server](source/language_server/README.md)

[syntax highlighting](source/syntax_highlighting/README.md)

[standard library](source/ustlib/README.md)

[build system](source/build_system/README.md)

[C++ header converter](source/cpp_header_converter/README.md)

[interpreter](source/interpreter/README.md)

[plugin for QtCreator](source/qt_creator_plugin/README.md)

[extension for Visual Studio](source/visual_studio_extension/README.md)

[documentation](source/docs/README.md)

[examples](source/examples/README.md)

[extra libraries](source/extra_libs/README.md)

### IDE support

[Ecode](https://github.com/SpartanJ/ecode/) has built-in Ü syntax highlighting, Ü language server support, debugging support.
It's recommended at least to try using it.

[QtCreator](https://www.qt.io/product/development-tools) may be used as Ü IDE.
There is a [syntax highlighting file](source/syntax_highlighting/README.md) for it.
Also it supports custom language servers, which allows using the Ü language server.

There is an Ü extension for Microsoft Visual Studio.
See [corresponding readme](source/visual_studio_extension/README.md) for details.

Many other IDEs may be used too.
Any IDE with possibility to specify a custom language server may be used for Ü code writing.
Some IDEs also allow creating custom syntax highlighting rules, one can create it themselves.

### Downloads

The compiler downloads are available on the actions page - as action artifacts.
It's recommended to use one of the latest builds of the *master* branch.

### Authors

U-00DC-Sprache

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

U-00DC-Sprache

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

Download README