[pull] master from ziglang:master by pull[bot] · Pull Request #42 · dgfug/zig

pull · 2021-11-02T22:29:24Z

See Commits and Changes for more details.

Can you help keep this open source service alive? 💖 Please sponsor : )

google-cla · 2021-11-15T22:31:22Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T23:37:12Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T23:59:17Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T00:42:17Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T01:07:11Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T19:56:13Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T20:04:41Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T21:27:26Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T21:34:34Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T21:36:44Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T21:37:57Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-16T21:38:47Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-17T00:53:48Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-17T00:55:34Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-17T00:57:33Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-18T18:02:44Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-18T18:19:55Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-18T18:51:43Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

llvm: fix up clobbers for valgrind requests

EVFILT_USER and NOTE_TRIGGER were wrong. Added missing ones along the way.

Child.start_suspended ported to posix

Misc. Windows subsystem refactorings

…tions`

The old doc comment mentioned a parameter `len` three times, but the function does not accept such a parameter - it is actually called `n`.

ld.lld fails with "truncated or malformed archive" errors when reading archive header field values that are not valid numbers.

Move/coalesce `CompressDebugSections` and `RcIncludes` enums to `std.zig`

A function that participates in a group but guarantees allocation of one unit of concurrency, or returns an error.

Teach `std.fs.path` about the wonderful world of Windows paths

build runner: update from std.Thread.Pool to std.Io

Co-authored-by: Andrew Kelley <andrew@ziglang.org>

…m_literal handling rl.resultType() returns null for inferred_ptr and destructure, so move that to the unreachable block.

- https://github.com/ziglang/zig-bootstrap -> https://codeberg.org/ziglang/zig-bootstrap - https://github.com/ziglang/qemu-static -> https://codeberg.org/ziglang/qemu-static - Add <...> around bare URLs - Link to tips inside README.md, rather than in CONTRIBUTING.md

This method is called on an identifier token, so let's rename the parameter to make this clear. This is also how it's named on most of the caller's sides.

It seems to me this was simply forgotten. Or there is some reason I don't know why this code doesn't work for `comptime_float`. For a more comprehensive fix, #24057 is the place to look.

KangarooTwelve is a family of two fast and secure extendable-output functions (XOFs): KT128 and KT256. These functions generalize traditional hash functions by allowing arbitrary output lengths. KangarooTwelve was designed by SHA-3 authors. It aims to deliver higher performance than the SHA-3 and SHAKE functions defined in FIPS 202, while preserving their flexibility and core security principles. On high-end platforms, it can take advantage of parallelism, whether through multiple CPU cores or SIMD instructions. As modern SHA-3 constructions, KT128 and KT256 can serve as general-purpose hash functions and can be used, for example, in key-derivation, and with arbitrarily large inputs. RFC9861: https://datatracker.ietf.org/doc/rfc9861/

Allow KT128 and KT256 to use multiple threads to quickly process very large inputs.

Improves performance by spawning less threads.

`ST` is the "string terminator" and what is actually prescribed in the standard for escape codes. Use of `BEL` as a terminator is apparently a historical oddity that persists for compatibility. Unfortunately, not all terminals support using `BEL`, including Ubuntu's new default terminal, Ptyxis. Using `ST` should make it work in more terminals. Further reading: - https://en.wikipedia.org/wiki/ANSI_escape_code#Operating_System_Command_sequences - https://ecma-international.org/wp-content/uploads/ECMA-48_5th_edition_june_1991.pdf

Add std.crypto.hash.sha3.{KT128,KT256} - RFC 9861. (#25593)

this file is first and foremost plain text, and rendered markdown second.

A very recent change seems to have made this slower.

It's been a while since this was renamed to .zig-cache.

pull Bot added the ⤵️ pull label Nov 2, 2021

GiuseppeCesarano and others added 11 commits November 7, 2025 08:53

std.Child: start_suspended ported to posix

f4159ef

Merge pull request #25848 from Rexicon226/llvm-valgrind-clobber

19af9fa

llvm: fix up clobbers for valgrind requests

sema: disallow slices of opaque types

92f6489

Fix kqueue definitions on NetBSD

852a1f7

EVFILT_USER and NOTE_TRIGGER were wrong. Added missing ones along the way.

Merge pull request #25820 from GiuseppeCesarano/process

bf15c79

Child.start_suspended ported to posix

Merge pull request #25158 from castholm/subsystem

74d2536

Misc. Windows subsystem refactorings

Move/coalesce CompressDebugSections enum to `std.zig.CompressDebugSec…

f587209

…tions`

Move/coalesce RcIncludes enum to std.zig.RcIncludes

da77d30

Fix param name in doc comment for std.Io.Reader.peek()

38d4440

The old doc comment mentioned a parameter `len` three times, but the function does not accept such a parameter - it is actually called `n`.

link.Elf: Ensure archive header fields are not left blank

43eb9b5

ld.lld fails with "truncated or malformed archive" errors when reading archive header field values that are not valid numbers.

Merge pull request #25860 from squeek502/coalesce-to-std-zig

be4eaed

Move/coalesce `CompressDebugSections` and `RcIncludes` enums to `std.zig`

GiuseppeCesarano and others added 30 commits November 24, 2025 21:32

std.Io.File.readPositional fixed buffer type

476d7d9

std.Io: add Group.concurrent

32dc46a

A function that participates in a group but guarantees allocation of one unit of concurrency, or returns an error.

build runner: update from std.Thread.Pool to std.Io

a242292

build runner: update Mutex and Condition usage to std.Io

3f34f5e

frontend: introduce error.Canceled

ece62a0

build runner: fix recursive locking of max_rss_mutex

8435318

Merge pull request #25993 from squeek502/windows-paths

53e615b

Teach `std.fs.path` about the wonderful world of Windows paths

Merge pull request #26037 from ziglang/build-runner-std.Io

5816646

build runner: update from std.Thread.Pool to std.Io

std.Io.Threaded: fix QueryPerformanceCounter usage

e4be00f

Co-authored-by: Andrew Kelley <andrew@ziglang.org>

std.testing: Fix expectEqualDeep formatted enum (#25960)

14ba3bd

std.Zig.AstGen: handle properly .inferred_ptr and .destructure in enu…

d0ba664

…m_literal handling rl.resultType() returns null for inferred_ptr and destructure, so move that to the unreachable block.

fetch: update from std.Thread.Pool to std.Io

0f1a6ae

ci: add aarch64-macos to Forgejo Actions

f50b0d7

ci: remove hardcoded paths in aarch64-macos scripts

6ef3af4

std.zig.AstGen: rename token_bytes parameter to ident_name_raw

f3270ce

This method is called on an identifier token, so let's rename the parameter to make this clear. This is also how it's named on most of the caller's sides.

Build.Step.Options: add comptime_float support

e23af9d

It seems to me this was simply forgotten. Or there is some reason I don't know why this code doesn't work for `comptime_float`. For a more comprehensive fix, #24057 is the place to look.

std.crypto.kt128: add support for threads

846082f

Allow KT128 and KT256 to use multiple threads to quickly process very large inputs.

crypto.blake3: sequentially process larger small tree layers (#26046)

5f73c01

Improves performance by spawning less threads.

std.elf implemented DynamicSectionBufferIterator

0b5b35c

Merge pull request #26005 from jedisct1/kt128r

2e328be

Add std.crypto.hash.sha3.{KT128,KT256} - RFC 9861. (#25593)

README: enhance plain text readability

fc8a51e

this file is first and foremost plain text, and rendered markdown second.

ci: make the workflow file a bit more readable

c969ef7

ci: bump riscv64-linux-debug timeout by 1 hour

43b4368

A very recent change seems to have made this slower.

ci: remove GitHub Actions

4d58faf

adjust issue templates for Codeberg

9b752cb

remove zig-cache from .gitignore

51bb2b3

It's been a while since this was renamed to .zig-cache.

README: migrated to codeberg

738d2be

Conversation

pull Bot commented Nov 2, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

google-cla Bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 17, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 17, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 17, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 18, 2021

pull Bot commented Nov 2, 2021 •

edited

Loading