0
Fork 0
mirror of https://codeberg.org/ziglang/zig synced 2026-11-18 07:05:05 +00:00
No description
  • Zig 97.5%
  • C 1.9%
  • C++ 0.2%
  • Python 0.1%
Find a file
Andrew Kelley 572cb24d1a progress towards semantic error serialization
Introduces std.zig.ErrorBundle which is a trivially serializeable set
of compilation errors. This is in the standard library so that both
the compiler and the build runner can use it. The idea is they will
use it to communicate compilation errors over a binary protocol.

The binary encoding of ErrorBundle is a bit problematic - I got a little
too aggressive with compaction. I need to change it in a follow-up
commit to use some indirection in the error message list, otherwise
iteration is too unergonomic. In fact it's so problematic right now that
the logic getAllErrorsAlloc() actually fails to produce a viable
ErrorBundle because it puts SourceLocation data in between the root
level ErrorMessage data.

This commit has a simplification - redundant logic for rendering AST
errors to stderr has been removed in favor of moving the logic for
lowering AST errors into AstGen. So even if we get parse errors, the
errors will get lowered into ZIR before being reported. I believe this
will be useful when working on --autofix. Either way, some redundant
brittle logic was happily deleted.

In Compilation, updateSubCompilation() is improved to properly perform
error reporting when a sub-compilation object fails. It no longer dumps
directly to stderr; instead it populates an ErrorBundle object, which
gets added to the parent one during getAllErrorsAlloc().

In package fetching code, instead of dumping directly to stderr, it now
populates an ErrorBundle object, and gets properly reported at the CLI
layer of abstraction.
History 2023-03-15 10:48:12 -07:00
.github CI: give x86_64-linux-release a little more time 2023-01-27 14:53:17 -07:00
ci CI: use -j1 like a coward 2023-03-15 10:48:12 -07:00
cmake Merge pull request #13514 from kcbanner/windows_build_fixes 2023-01-05 17:26:32 -07:00
doc Resolve docs inconsistency with Overflow builtins 2023-03-13 14:47:20 +00:00
lib progress towards semantic error serialization 2023-03-15 10:48:12 -07:00
src progress towards semantic error serialization 2023-03-15 10:48:12 -07:00
stage1 Include signal.h to define SIGTRAP in Stage 1 compiler (#14867) 2023-03-10 13:36:43 +00:00
test CI: use -j1 like a coward 2023-03-15 10:48:12 -07:00
tools tools: fix typo in lldb command 2023-03-15 00:01:44 -04:00
.gitattributes update gitattributes and move test data into subdir 2022-12-18 16:28:30 -07:00
.gitignore std/build: change default install prefix to zig-out 2021-04-29 23:58:45 +02:00
build.zig build system: capture stderr and report it later 2023-03-15 10:48:12 -07:00
CMakeLists.txt extract ThreadPool and WaitGroup from compiler to std lib 2023-03-15 10:48:12 -07:00
LICENSE Happy new year! 🎉 (#14143) 2022-12-31 18:13:00 +00:00
README.md move some files to the .github directory 2022-03-24 12:22:23 -07:00

ZIG

A general-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

Resources

Installation

License

The ultimate goal of the Zig project is to serve users. As a first-order effect, this means users of the compiler, helping programmers to write better software. Even more important, however, are the end-users.

Zig is intended to be used to help end-users accomplish their goals. Zig should be used to empower end-users, never to exploit them financially, or to limit their freedom to interact with hardware or software in any way.

However, such problems are best solved with social norms, not with software licenses. Any attempt to complicate the software license of Zig would risk compromising the value Zig provides.

Therefore, Zig is available under the MIT (Expat) License, and comes with a humble request: use it to make software better serve the needs of end-users.

This project redistributes code from other projects, some of which have other licenses besides MIT. Such licenses are generally similar to the MIT license for practical purposes. See the subdirectories and files inside lib/ for more details.