avatar_url
stringlengths 46
116
⌀ | name
stringlengths 1
46
| full_name
stringlengths 7
60
| created_at
stringdate 2016-04-01 08:17:56
2025-05-20 11:38:17
| description
stringlengths 0
387
⌀ | default_branch
stringclasses 45
values | open_issues
int64 0
4.93k
| stargazers_count
int64 0
78.2k
| forks_count
int64 0
3.09k
| watchers_count
int64 0
78.2k
| tags_url
stringlengths 0
94
| license
stringclasses 27
values | topics
listlengths 0
20
| size
int64 0
4.82M
| fork
bool 2
classes | updated_at
stringdate 2018-11-13 14:41:18
2025-05-22 08:23:54
| has_build_zig
bool 2
classes | has_build_zig_zon
bool 2
classes | zig_minimum_version
stringclasses 60
values | repo_from
stringclasses 3
values | dependencies
listlengths 0
121
| readme_content
stringlengths 0
437k
| dependents
listlengths 0
21
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://avatars.githubusercontent.com/u/9899175?v=4 | zig-nats | rutgerbrf/zig-nats | 2021-07-01T22:31:19Z | Work-in-progress NATS library for Zig | master | 0 | 4 | 0 | 4 | https://api.github.com/repos/rutgerbrf/zig-nats/tags | Apache-2.0 | [
"nats",
"zig"
]
| 20 | false | 2023-07-17T06:29:21Z | true | false | unknown | github | []
| A NATS client for Zig | []
|
https://avatars.githubusercontent.com/u/5075628?v=4 | glinka | oetherington/glinka | 2021-09-09T20:52:00Z | A fast Typescript compiler written in Zig | main | 3 | 4 | 0 | 4 | https://api.github.com/repos/oetherington/glinka/tags | AGPL-3.0 | [
"compiler",
"transpiler",
"typescript",
"zig"
]
| 1,196 | false | 2024-11-25T01:20:51Z | true | false | unknown | github | []
| Glinka
<a></a>
<a></a>
<a></a>
Glinka is a Typescript compiler written in Zig designed for speed. Please note
that it is still a work in progress and large portions of the language are not
yet implemented. For a general overview of what's already available you can look
in the <code>integration/tests</code> directory and at the <code>TODO</code> file.
Building
You will need the <a>Zig compiler</a> to build
Glinka. Glinka is kept up-to-date with the HEAD of the Zig master branch.
Create a debug build: <code>make</code>.
Create a production build: <code>make release</code>.
Run unit tests: <code>make test</code>.
Create a unit test coverage report (requires <code>kcov</code> to be installed):
<code>make coverage</code>.
Run integration tests (you must run <code>npm install</code> before the first time):
<code>make integration</code>.
Contributing
Pull requests and bug reports are welcome
<a>on Github</a>.
Contributors should follow the
<a>Contributor Covenant</a>.
Copying
Glinka is free-software under the
<a>GNU AGPLv3</a> (see the included
<code>COPYING</code> file for more information). | []
|
https://avatars.githubusercontent.com/u/7270159?v=4 | zig-mbedtls | mattnite/zig-mbedtls | 2021-12-17T16:49:52Z | compile mbedtls in your build.zig | main | 1 | 4 | 7 | 4 | https://api.github.com/repos/mattnite/zig-mbedtls/tags | MIT | [
"build",
"mbedtls",
"tls",
"zig",
"zig-package"
]
| 20 | false | 2024-10-25T15:52:17Z | true | false | unknown | github | []
| mbedtls build package
<a></a>
Like this project?
If you like this project or other works of mine, please consider <a>donating to or sponsoring me</a> on Github <a>:heart:</a>
How to use
This repo contains code for your <code>build.zig</code> that can statically compile mbedtls.
Link to your application
In order to statically link mbedtls into your application:
```zig
const mbedtls = @import("path/to/mbedtls.zig");
pub fn build(b: *std.build.Builder) void {
// ...
<code>const lib = mbedtls.create(b, target, optimize);
const exe = b.addExecutable(.{
.name = "my-program",
.root_source_file = .{ .path = "src/main.zig" },
.target = target,
.optimize = optimize,
});
lib.link(exe);
</code>
}
``` | []
|
https://avatars.githubusercontent.com/u/9899175?v=4 | zig-nkeys | rutgerbrf/zig-nkeys | 2021-05-20T21:58:04Z | NKeys support for Zig | master | 0 | 3 | 1 | 3 | https://api.github.com/repos/rutgerbrf/zig-nkeys/tags | Apache-2.0 | [
"nats",
"nkeys",
"zig"
]
| 116 | false | 2025-02-28T15:57:31Z | true | true | unknown | github | []
| NKeys support for Zig
<a></a>
<a></a>
Still a work in progress, things will definitely change!
Contains a tool called <code>znk</code> which is a clone of the <a><code>nk</code> tool</a>.
Building
Zig master works at the time of writing.
Use <code>zig build znk</code> to build the <code>znk</code> tool.
The <code>znk</code> tool can be run by using <code>zig build run-znk</code>.
Tests for the library can be run by using <code>zig build test</code>.
Tests for the <code>znk</code> tool can be run by using <code>zig build test-znk</code>. | []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | zig-scrypt | x13a/zig-scrypt | 2021-03-05T08:05:21Z | The scrypt key derivation function in zig. | master | 0 | 3 | 2 | 3 | https://api.github.com/repos/x13a/zig-scrypt/tags | MIT | [
"crypto",
"scrypt",
"zig",
"zig-lang"
]
| 268 | false | 2023-01-28T04:33:12Z | true | false | unknown | github | []
| zig-scrypt
The scrypt key derivation function in zig.
Merged: <a>9577</a>
Reference
<ul>
<li><a>rfc</a></li>
<li><a>golang</a></li>
<li><a>c</a></li>
</ul> | []
|
https://avatars.githubusercontent.com/u/140233641?v=4 | headstart | kora-org/headstart | 2021-10-17T04:37:17Z | A modern UEFI bootloader. | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/kora-org/headstart/tags | MIT | [
"bootloader",
"uefi",
"x86",
"zig"
]
| 160 | false | 2024-09-27T11:44:03Z | true | true | unknown | github | [
{
"commit": "6ef01c114e8f485d1c2afc829747b017fcbf157c.tar.gz",
"name": "limine",
"tar_url": "https://github.com/leap0x7b/limine/archive/6ef01c114e8f485d1c2afc829747b017fcbf157c.tar.gz.tar.gz",
"type": "remote",
"url": "https://github.com/leap0x7b/limine"
}
]
| Headstart
A modern UEFI bootloader. Part of the Kora operating system. | []
|
https://avatars.githubusercontent.com/u/4425925?v=4 | zig-plotille | tammoippen/zig-plotille | 2021-07-09T08:41:08Z | Plot graphs and histograms in the terminal. | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/tammoippen/zig-plotille/tags | - | [
"ansi-colors",
"braille",
"graph",
"histogram",
"plot",
"terminal",
"zig",
"zig-library",
"zig-package",
"ziglang"
]
| 105 | false | 2025-02-02T13:39:11Z | true | false | unknown | github | []
|
zig-plotille
Draw in the terminal.
<ul>
<li>Use colors: ansi, 8bit or true color, if your terminal allows.</li>
<li>Have a canvas for general braille dots drawing.</li>
<li>Have a crappy hist implementation (TODO insert link).</li>
<li>Have a figure for scatter plots, histograms, line plots. Also supports text and vline, vspan, hline, hspan.</li>
</ul>
Re-implementation of the (python) <a>plotille</a> with the intention to (at some point) provide a C-API as well.
For usage (for now) have a look at the examples/ and also in the code (tests). | []
|
https://avatars.githubusercontent.com/u/7495216?v=4 | batnotifyd | evan-goode/batnotifyd | 2021-06-07T00:42:28Z | Lightweight daemon for low battery notifications on GNU/Linux | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/evan-goode/batnotifyd/tags | GPL-3.0 | [
"zig"
]
| 41 | false | 2024-07-30T18:22:20Z | true | false | unknown | github | []
| batnotifyd
Lightweight daemon for low battery notifications on GNU/Linux. Requires libudev and libnotify. Written in <a>Zig</a>.
Build & Run
<code>nix develop # if using Nix
zig build -Drelease-safe
./zig-out/bin/batnotifyd</code>
Recommended usage
batnotifyd can run a command if the battery gets "dangerously low" (default is 2%, configure with <code>--danger_threshold</code>). It's highly recommended to set it to suspend, or hibernate if your system supports it:
<code>./zig-out/bin/batnotifyd --danger_hook 'systemctl suspend'</code>
Install
A systemd <code>--user</code> unit file is included for convenience.
<code>zig build
sudo install -m 755 ./zig-out/bin/batnotifyd /usr/local/bin/
install -Dm 644 batnotifyd.service -t ~/.config/systemd/user/
systemctl --user daemon-reload
systemctl --user enable --now batnotifyd</code> | []
|
https://avatars.githubusercontent.com/u/39484230?v=4 | sharko | zenith391/sharko | 2021-09-21T06:53:27Z | A Zig editor made in Zig but 2.0 | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/zenith391/sharko/tags | GPL-3.0 | [
"zig"
]
| 73 | false | 2023-01-13T05:31:37Z | true | false | unknown | github | []
| Sharko
A Zig editor made in Zig. | []
|
https://avatars.githubusercontent.com/u/271548?v=4 | raytracing-one-weekend-zig | damienfir/raytracing-one-weekend-zig | 2021-03-16T12:25:09Z | Zig implementation of the book Ray Tracing in One Weekend https://raytracing.github.io/books/RayTracingInOneWeekend.html | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/damienfir/raytracing-one-weekend-zig/tags | - | [
"raytracing",
"zig"
]
| 182 | false | 2022-04-26T12:22:49Z | true | false | unknown | github | []
| Ray Tracing in One Weekend in Zig
Usage:
<code>zig build run -Drelease-fast > image.ppm</code>
Final image at the end of book 1:
Book 2, chapter 1: Moving spheres
https://raytracing.github.io/books/RayTracingInOneWeekend.html | []
|
https://avatars.githubusercontent.com/u/2528778?v=4 | zanzara | rbino/zanzara | 2021-06-14T18:38:24Z | Allocation-free, I/O-agnostic MQTT client written in Zig | main | 1 | 3 | 1 | 3 | https://api.github.com/repos/rbino/zanzara/tags | MIT | [
"mqtt",
"mqtt-client",
"zig"
]
| 89 | false | 2024-07-16T08:57:01Z | true | false | unknown | github | []
| zanzara
<a></a>
An allocation-free, I/O-agnostic MQTT client written in Zig.
<em>Warning: this is a work in progress, the API is subject to change</em>
Features
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> MQTT 3.1.1 client packet serialization/deserialization
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> Ping handling
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> Subscribe and receive data
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> Publish (QoS 0 only)
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> Unsubscribe
<br/><input type='checkbox' class='w-4 h-4 text-blue-600 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' disabled></input> Everything else (including a more detailed list of what's missing)
Example
You can run the example with:
<code>zig run example.zig</code>
You can use <code>mosquitto_sub</code> to see the message that is published by the example just after the
connection
<code>mosquitto_sub -h "mqtt.eclipseprojects.io" -t "zig/zanzara_out"</code>
You can use also <code>mosquitto_pub</code> to publish to the topic the example subscribes to
<code>mosquitto_pub -h "mqtt.eclipseprojects.io" -t "zig/zanzara_in" -m "Hello, MQTT"</code> | []
|
https://avatars.githubusercontent.com/u/63115601?v=4 | ed25519-donna-zig | lithdew/ed25519-donna-zig | 2021-07-04T04:04:02Z | Minimal Zig bindings to ed25519-donna. | master | 1 | 3 | 0 | 3 | https://api.github.com/repos/lithdew/ed25519-donna-zig/tags | - | [
"ed25519",
"zig"
]
| 8 | false | 2025-02-05T08:26:45Z | true | false | unknown | github | []
| ed25519-donna-zig
Minimal <a>Zig</a> bindings to <a>ed25519-donna</a>.
ed25519-donna is <a>Andrew Moon</a>'s implementation of ed25519 signing, verification, and batch verification.
These bindings require that the OpenSSL crypto library is available in your environment for cryptographically-secure random number generation and SHA-512 hashing.
Support for custom hash functions and random number generation functions is not available at the moment, but will be made available once Zig's standard library implementation of SHA-512 hashing yields better benchmark results.
In order to generate ed25519 keys, refer to Zig's standard library ed25519 implementation. If you have a need for ed25519-donna's key generation implementation, please file an issue describing your use case.
These bindings were built and tested against Zig's master branch over all possible optimization modes.
Motivation
These bindings were built for a few applications I am working on that makes heavy use of Ed25519 signing and batch verification. I found Zig's standard library ed25519 implementation to be a tad too slow, so I wrote some bindings to ed25519-donna instead.
When the time comes that Zig's standard library ed25519 implementation yields better benchmark results, it should be trivial to migrate over to making use of Zig's standard library ed25519 implementation as these bindings feature API parity with Zig's standard library ed25519 implementation.
Setup
In your build.zig:
```zig
const exe = b.addExecutable("your_executable_here", "main.zig");
// ... set target, build mode, and other settings here.
exe.linkLibC();
exe.linkSystemLibrary("crypto");
exe.addIncludeDir("ed25519-donna-zig/lib");
var defines: std.ArrayListUnmanaged([]const u8) = .{};
defer defines.deinit(exe.builder.allocator);
if (std.Target.x86.featureSetHas(exe.target.getCpuFeatures(), .sse2)) {
defines.append(exe.builder.allocator, "-DED25519_SSE2") catch unreachable;
}
exe.addCSourceFile("ed25519-donna-zig/lib/ed25519.c", defines.items);
exe.addPackagePath("ed25519-donna", "ed25519-donna-zig/ed25519.zig");
```
Example
```zig
test "ed25519: sign and verify a message" {
const ed25519 = @import("ed25519-donna");
<code>const keys = try std.crypto.sign.Ed25519.KeyPair.create(null);
const message = "hello world";
const signature = try ed25519.sign(message, keys);
try ed25519.verify(signature, message, keys.public_key);
</code>
}
test "ed25519: verify a batch of signatures using verifyBatch()" {
const ed25519 = @import("ed25519-donna");
<code>const keys = try std.crypto.sign.Ed25519.KeyPair.create(null);
const message = "hello world";
const signature = try ed25519.sign(message, keys);
var batch: [64]std.crypto.sign.Ed25519.BatchElement = undefined;
for (batch) |*element| {
element.* = .{
.sig = signature,
.msg = message,
.public_key = keys.public_key,
};
}
try ed25519.verifyBatch(64, batch);
</code>
}
test "ed25519: verify a batch of signatures using the BatchVerifier API" {
const ed25519 = @import("ed25519-donna");
<code>const keys = try std.crypto.sign.Ed25519.KeyPair.create(null);
const message = "hello world";
const signature = try ed25519.sign(message, keys);
var verifier: ed25519.BatchVerifier = .{};
defer verifier.deinit(testing.allocator);
var i: usize = 0;
while (i < 64) : (i += 1) {
try verifier.add(testing.allocator, .{
.public_key = &keys.public_key,
.signature = &signature,
.message = message,
});
}
const results = try verifier.verify();
try testing.expect(std.mem.allEqual(c_int, results, 1));
</code>
}
```
Benchmarks
Single-threaded and multi-threaded benchmarks which compares the performance of these bindings to the Zig standard library's ed25519 implementation may be found <a>here</a>.
For the single-threaded benchmarks, ed25519 signing, verification, and batch verification are performed 100,000 times. For the multi-threaded benchmarks, ed25519 signing, verification, and batch verification are performed 500,000 times.
The benchmarks make use of the generic thread pool implementation available in the source code of Zig's self-hosted compiler.
Results from running these benchmarks on my laptop may be found below. Take these benchmarks and results with a grain of salt.
```
$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
$ zig build bench -Drelease-fast
=== ed25519-std (single thread) ===
sign: took 6.0919 second(s)
sign: 16415.1814 signatures/sec
verify: took 7.5878 second(s)
verify: 13179.0926 signatures/sec
batch_verify(1): took 16.2880 second(s)
batch_verify(1): 6139.4747 signatures/sec
batch_verify(2): took 10.2503 second(s)
batch_verify(2): 9755.7721 signatures/sec
batch_verify(4): took 7.0835 second(s)
batch_verify(4): 14117.2217 signatures/sec
batch_verify(8): took 5.2012 second(s)
batch_verify(8): 19226.2152 signatures/sec
batch_verify(16): took 4.4654 second(s)
batch_verify(16): 22394.4535 signatures/sec
batch_verify(32): took 3.6738 second(s)
batch_verify(32): 27219.8045 signatures/sec
batch_verify(64): took 3.5673 second(s)
batch_verify(64): 28032.4098 signatures/sec
batch_verify(128): took 3.5383 second(s)
batch_verify(128): 28262.1541 signatures/sec
batch_verify(256): took 3.7326 second(s)
batch_verify(256): 26791.3165 signatures/sec
batch_verify(512): took 3.5267 second(s)
batch_verify(512): 28354.9587 signatures/sec
batch_verify(1024): took 3.6137 second(s)
batch_verify(1024): 27672.1112 signatures/sec
batch_verify(2048): took 3.7741 second(s)
batch_verify(2048): 26496.2290 signatures/sec
batch_verify(4096): took 4.0136 second(s)
batch_verify(4096): 24915.1312 signatures/sec
=== ed25519-std (multiple threads) ===
sign(1): took 8.4394 second(s)
sign(1): 59246.0867 signatures/sec
verify(1): took 10.4988 second(s)
verify(1): 47624.6976 signatures/sec
batch_verify(1): took 22.2592 second(s)
batch_verify(1): 22462.6215 signatures/sec
batch_verify(2): took 12.7288 second(s)
batch_verify(2): 39280.8696 signatures/sec
batch_verify(4): took 8.7091 second(s)
batch_verify(4): 57411.1779 signatures/sec
batch_verify(8): took 7.0137 second(s)
batch_verify(8): 71289.1977 signatures/sec
batch_verify(16): took 5.4052 second(s)
batch_verify(16): 92503.5592 signatures/sec
batch_verify(32): took 4.6896 second(s)
batch_verify(32): 106618.9187 signatures/sec
batch_verify(64): took 5.0738 second(s)
batch_verify(64): 98545.5489 signatures/sec
batch_verify(128): took 4.4141 second(s)
batch_verify(128): 113272.1161 signatures/sec
batch_verify(256): took 4.2404 second(s)
batch_verify(256): 117914.0667 signatures/sec
batch_verify(512): took 4.2700 second(s)
batch_verify(512): 117097.2778 signatures/sec
batch_verify(1024): took 4.5000 second(s)
batch_verify(1024): 111111.7824 signatures/sec
batch_verify(2048): took 4.9844 second(s)
batch_verify(2048): 100312.7273 signatures/sec
batch_verify(4096): took 4.7750 second(s)
batch_verify(4096): 104711.3968 signatures/sec
=== ed25519-donna (single thread) ===
sign: took 2.2230 second(s)
sign: 44985.2332 signatures/sec
verify: took 6.2735 second(s)
verify: 15940.1595 signatures/sec
batch_verify(1): took 6.0811 second(s)
batch_verify(1): 16444.2659 signatures/sec
batch_verify(2): took 6.3051 second(s)
batch_verify(2): 15860.2567 signatures/sec
batch_verify(4): took 5.1554 second(s)
batch_verify(4): 19397.3004 signatures/sec
batch_verify(8): took 4.1382 second(s)
batch_verify(8): 24165.0065 signatures/sec
batch_verify(16): took 3.6343 second(s)
batch_verify(16): 27515.2660 signatures/sec
batch_verify(32): took 3.3876 second(s)
batch_verify(32): 29519.5212 signatures/sec
batch_verify(64): took 3.1428 second(s)
batch_verify(64): 31818.7612 signatures/sec
batch_verify(128): took 3.3215 second(s)
batch_verify(128): 30107.2936 signatures/sec
batch_verify(256): took 3.1791 second(s)
batch_verify(256): 31455.2151 signatures/sec
batch_verify(512): took 3.3029 second(s)
batch_verify(512): 30276.1243 signatures/sec
batch_verify(1024): took 3.2536 second(s)
batch_verify(1024): 30735.0100 signatures/sec
batch_verify(2048): took 3.1686 second(s)
batch_verify(2048): 31559.9908 signatures/sec
batch_verify(4096): took 3.3008 second(s)
batch_verify(4096): 30295.6094 signatures/sec
=== ed25519-donna (multiple threads) ===
sign(1): took 2.4315 second(s)
sign(1): 205634.2979 signatures/sec
verify(1): took 6.9973 second(s)
verify(1): 71456.5081 signatures/sec
batch_verify(1): took 7.2783 second(s)
batch_verify(1): 68697.8065 signatures/sec
batch_verify(2): took 7.3983 second(s)
batch_verify(2): 67582.6513 signatures/sec
batch_verify(4): took 6.5533 second(s)
batch_verify(4): 76297.7575 signatures/sec
batch_verify(8): took 5.2693 second(s)
batch_verify(8): 94889.5635 signatures/sec
batch_verify(16): took 4.5523 second(s)
batch_verify(16): 109834.6577 signatures/sec
batch_verify(32): took 4.1214 second(s)
batch_verify(32): 121318.9474 signatures/sec
batch_verify(64): took 3.7905 second(s)
batch_verify(64): 131909.4312 signatures/sec
batch_verify(128): took 3.6549 second(s)
batch_verify(128): 136803.2566 signatures/sec
batch_verify(256): took 3.7900 second(s)
batch_verify(256): 131924.9328 signatures/sec
batch_verify(512): took 3.7148 second(s)
batch_verify(512): 134596.8465 signatures/sec
batch_verify(1024): took 3.7415 second(s)
batch_verify(1024): 133637.4161 signatures/sec
batch_verify(2048): took 3.7712 second(s)
batch_verify(2048): 132583.3362 signatures/sec
batch_verify(4096): took 3.7512 second(s)
batch_verify(4096): 133289.6401 signatures/sec
``` | []
|
https://avatars.githubusercontent.com/u/13452083?v=4 | junk | eriktate/junk | 2021-11-07T22:39:04Z | A _very_ early in development, platform adventure game | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/eriktate/junk/tags | NOASSERTION | [
"game",
"game-development",
"game-engine",
"gamedev",
"zig",
"ziglang"
]
| 2,534 | false | 2023-06-19T18:06:28Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/7967463?v=4 | aoc | natecraddock/aoc | 2021-12-01T19:31:16Z | Advent of Code puzzle solutions | master | 0 | 3 | 1 | 3 | https://api.github.com/repos/natecraddock/aoc/tags | Unlicense | [
"advent-of-code",
"advent-of-code-2021",
"adventofcode",
"zig"
]
| 66 | false | 2023-07-25T14:52:06Z | false | false | unknown | github | []
| Advent Of Code
My solutions to the Advent of Code.
<ul>
<li><a>2021</a>: Solve all problems in Zig to learn the language better</li>
<li><a>2023</a>: Use Lua and focus on completion not speed</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/53620720?v=4 | linked-lists-in-zig | willdoescode/linked-lists-in-zig | 2021-03-22T22:28:17Z | Linked list implementation in zig. | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/willdoescode/linked-lists-in-zig/tags | - | [
"linked-list",
"zig"
]
| 63 | false | 2021-09-24T22:45:14Z | true | false | unknown | github | []
| Linked Lists In Zig
| []
|
https://avatars.githubusercontent.com/u/657412?v=4 | zig-examples | donsez/zig-examples | 2021-08-05T08:50:56Z | Ziglang examples | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/donsez/zig-examples/tags | - | [
"zig"
]
| 5 | false | 2024-07-30T16:02:29Z | false | false | unknown | github | []
| Zig :: Examples
Zig is a general-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
https://ziglang.org/
https://ziglang.org/documentation/master/#Introduction
Installation
Tarball
<code>bash
cd ~/devtools
wget https://ziglang.org/builds/zig-macos-x86_64-0.9.0-dev.729+bd8baefaa.tar.xz
xz -d zig-macos-x86_64-0.9.0-dev.729+bd8baefaa.tar.xz
PATH=$PATH:~/devtools/zig-macos-x86_64-0.9.0-dev.729+bd8baefaa
zig env</code>
Brew
<code>bash
brew install zig</code>
From Git HEAD
<code>bash
brew install zig --HEAD</code>
Examples
Hello World !
```bash
cd hello
zig build-exe hello.zig
wc -c hello
./hello
zig build-exe hello.zig -O ReleaseSmall --strip --single-threaded
wc -c hello
zig build-exe hello.zig -O ReleaseSmall --strip --single-threaded -target x86_64-macos
wc -c hello
file hello
```
Global variables
<code>bash
cd global_variables
zig test global_variables.zig</code>
Errors
TODO
Test
<code>bash
cd test_null
zig test test_null.zig</code>
C library (libcurl)
<code>bash
cd curl
zig build-exe curl.zig</code>
<blockquote>
See https://ziglearn.org/chapter-4/
</blockquote>
Config
<code>bash
cd config/
zig build-exe config.zig
./config</code>
Comptime
TODO
Async
TODO
<blockquote>
See https://ziglearn.org/chapter-5/
</blockquote>
Allocator
TODO
<blockquote>
See https://ziglearn.org/chapter-2/#allocators
</blockquote>
Cross compile
```bash
cd cross-compile-arm/
zig targets
zig targets | jq .arch
zig targets | jq .os
zig targets | jq .abi
zig targets | jq .libc
zig build-exe hello.zig -target armeb-linux-musleabi --library c --strip --single-threaded
file hello
```
<blockquote>
See https://ziglearn.org/chapter-3/#cross-compilation
</blockquote>
Benchmarks
<code>bash
cd benchmark/
./benchmark.sh</code>
<blockquote>
See https://github.com/Sahnvour/zig-benchmark
See https://benchmarksgame-team.pages.debian.net/benchmarksgame/why-measure-toy-benchmark-programs.html
See https://github.com/tiehuis/zig-benchmarks-game
</blockquote>
Resources
<ul>
<li>https://ziglearn.org/</li>
<li>https://github.com/ziglang/zig/tree/master/test</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/96184617?v=4 | zigbraten | ynuwenhof-zz/zigbraten | 2022-01-30T13:14:22Z | Internal cheat for Cube 2: Sauerbraten written in Zig | master | 0 | 3 | 1 | 3 | https://api.github.com/repos/ynuwenhof-zz/zigbraten/tags | MIT | [
"aimbot",
"cheat",
"internal",
"zig"
]
| 8 | false | 2023-10-04T23:47:53Z | true | false | unknown | github | []
| zigbraten
Proof of concept internal cheat for <a>Cube 2: Sauerbraten</a> written in <a>Zig</a>.
Features
<ul>
<li><strong>Aimbot</strong>, right shift key</li>
</ul>
Usage
<ol>
<li>Clone the repo by running <code>git clone https://github.com/ynuwenhof/zigbraten.git</code></li>
<li>Install Zig from <a>here</a></li>
<li>Build the dll by running <code>zig build</code></li>
<li>Inject the dll into the game using any dll injector</li>
</ol>
Toggle the features with their hotkeys.
TODO
<ul>
<li>More features</li>
<li>Overlay for GUI and ESP</li>
<li>Add some kind of module system to manage all the features</li>
</ul>
This is my first Zig project ever so this code might not be that great.
| []
|
https://avatars.githubusercontent.com/u/29869612?v=4 | ziglings-nix | jakeisnt/ziglings-nix | 2021-03-26T19:41:00Z | Learn the Zig programming language by fixing tiny broken programs - with the Nix build system! | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/jakeisnt/ziglings-nix/tags | MIT | [
"direnv",
"flakes",
"nix",
"nix-flakes",
"zig",
"ziglang",
"ziglings"
]
| 186 | true | 2025-02-19T01:14:36Z | true | false | unknown | github | []
| Ziglings
Welcome to Ziglings! This project contains a series of tiny broken programs.
By fixing them, you'll learn how to read and write
<a>Zig</a>
code.
Those tiny broken programs need your help! (You'll also save the planet from
evil aliens and help some friendly elephants stick together, which is very
sweet of you.)
This project was directly inspired by the brilliant and fun
<a>rustlings</a>
project for the <a>Rust</a> language.
Indirect inspiration comes from <a>Ruby Koans</a>
and the Little LISPer/Little Schemer series of books.
Intended Audience
This will probably be difficult if you've <em>never</em> programmed before.
But no specific programming experience is required. And in particular,
you are <em>not</em> expected to have any prior experience with "systems programming"
or a "systems" level language such as C.
Each exercise is self-contained and self-explained. However, you're encouraged
to also check out these Zig language resources for more detail:
<ul>
<li>https://ziglearn.org/</li>
<li>https://ziglang.org/documentation/master/</li>
</ul>
Also, the <a>Zig community</a> is incredibly friendly and helpful!
Getting Started
Install a <a>development build</a> of the Zig compiler.
(See the "master" section of the downloads page.)
Verify the installation and build number of <code>zig</code> like so:
<code>bash
$ zig version
0.8.0-dev.1065+xxxxxxxxx</code>
Clone this repository with Git:
<code>bash
$ git clone https://github.com/ratfactor/ziglings
$ cd ziglings</code>
Then run <code>zig build</code> and follow the instructions to begin!
<code>bash
$ zig build</code>
A Note About Versions
The Zig language is under very active development. In order to be current,
Ziglings tracks <strong>development</strong> builds of the Zig compiler rather than
versioned <strong>release</strong> builds. The last stable release was <code>0.7.1</code>, but Ziglings
needs a dev build with pre-release version "0.8.0" and a build number at least
as high as that shown in the example version check above.
It is likely that you'll download a build which is <em>greater</em> than the minimum.
Once you have a build of the Zig compiler that works with Ziglings, they'll
continue to work together. But keep in mind that if you update one, you may
need to also update the other.
Advanced Usage
It can be handy to check just a single exercise or <em>start</em> from a single
exercise:
<code>bash
zig build 19
zig build 19_start</code>
You can also run without checking for correctness:
<code>bash
zig build 19_test</code>
Or skip the build system entirely and interact directly with the compiler
if you're into that sort of thing:
<code>bash
zig run exercises/001_hello.zig</code>
Calling all wizards: To prepare an executable for debugging, install it
to zig-cache/bin with:
<code>bash
zig build 19_install</code>
TODO
Contributions are very welcome! I'm writing this to teach myself and to create
the learning resource I wished for. There will be tons of room for improvement:
<ul>
<li>Wording of explanations</li>
<li>Idiomatic usage of Zig</li>
<li>Additional exercises</li>
</ul>
Planned exercises:
<ul>
<li>[x] Hello world (main needs to be public)</li>
<li>[x] Importing standard library</li>
<li>[x] Assignment</li>
<li>[x] Arrays</li>
<li>[x] Strings</li>
<li>[x] If</li>
<li>[x] While</li>
<li>[x] For</li>
<li>[x] Functions</li>
<li>[x] Errors (error/try/catch/if-else-err)</li>
<li>[x] Defer (and errdefer)</li>
<li>[x] Switch</li>
<li>[x] Unreachable</li>
<li>[x] Enums</li>
<li>[x] Structs</li>
<li>[x] Pointers</li>
<li>[x] Optionals</li>
<li>[x] Struct methods</li>
<li>[x] Slices</li>
<li>[x] Many-item pointers</li>
<li>[x] Unions</li>
<li>[ ] Numeric types (integers, floats)</li>
<li>[ ] Labelled blocks and loops</li>
<li>[ ] Loops as expressions</li>
<li>[ ] Comptime</li>
<li>[ ] Inline loops (how to DEMO this?)</li>
<li>[ ] Anonymous structs</li>
<li>[ ] Sentinel termination</li>
<li>[ ] Vectors</li>
<li>[ ] Imports</li>
<li>[ ] Allocators</li>
<li>[ ] Arraylist</li>
<li>[ ] Filesystem</li>
<li>[ ] Readers and Writers</li>
<li>[ ] Formatting</li>
<li>[ ] JSON</li>
<li>[ ] Random Numbers</li>
<li>[ ] Crypto</li>
<li>[ ] Threads</li>
<li>[ ] Hash Maps</li>
<li>[ ] Stacks</li>
<li>[ ] Sorting</li>
<li>[ ] Iterators</li>
<li>[ ] Formatting specifiers</li>
<li>[ ] Advanced Formatting</li>
<li>[ ] Suspend / Resume</li>
<li>[ ] Async / Await</li>
<li>[ ] Nosuspend</li>
<li>[ ] Async Frames, Suspend Blocks</li>
</ul>
The initial topics for these exercises were unabashedly cribbed from
<a>ziglearn.org</a>. I've since moved things around
in an order that I think best lets each topic build upon each other. | []
|
https://avatars.githubusercontent.com/u/15616419?v=4 | to-the-core | Gertkeno/to-the-core | 2022-01-23T15:50:17Z | wasm4 gem collecting and super digging game | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/Gertkeno/to-the-core/tags | - | [
"game",
"wasm4",
"zig"
]
| 106 | false | 2024-12-03T03:24:58Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/65933340?v=4 | Zag | seanpm2001/Zag | 2022-01-04T01:49:23Z | Zag is a lightweight IDE for the Zig programming language. Zig *ZAG* \/\/\/ | ZigZag | 1 | 3 | 1 | 3 | https://api.github.com/repos/seanpm2001/Zag/tags | GPL-3.0 | [
"gpl3",
"gplv3",
"ide",
"md",
"txt",
"zag",
"zag-ide",
"zig",
"zig-lang",
"zig-zag",
"ziglang",
"zigzag"
]
| 464 | false | 2025-05-05T15:35:49Z | false | false | unknown | github | []
|
<a></a>
By:
<a>Seanpm2001</a>, <a></a> Et; Al.
Top
<code>README.md</code>
Read this article in a different language
<strong>Sorted by:</strong> <code>A-Z</code>
<a>Sorting options unavailable</a>
( <a>af Afrikaans</a> Afrikaans | <a>sq Shqiptare</a> Albanian | <a>am አማርኛ</a> Amharic | <a>ar عربى</a> Arabic | <a>hy հայերեն</a> Armenian | <a>az Azərbaycan dili</a> Azerbaijani | <a>eu Euskara</a> Basque | <a>be Беларуская</a> Belarusian | <a>bn বাংলা</a> Bengali | <a>bs Bosanski</a> Bosnian | <a>bg български</a> Bulgarian | <a>ca Català</a> Catalan | <a>ceb Sugbuanon</a> Cebuano | <a>ny Chichewa</a> Chichewa | <a>zh-CN 简体中文</a> Chinese (Simplified) | <a>zh-t 中國傳統的）</a> Chinese (Traditional) | <a>co Corsu</a> Corsican | <a>hr Hrvatski</a> Croatian | <a>cs čeština</a> Czech | <a>da dansk</a> Danish | <a>nl Nederlands</a> Dutch | <a><strong>en-us English</strong></a> English | <a>EO Esperanto</a> Esperanto | <a>et Eestlane</a> Estonian | <a>tl Pilipino</a> Filipino | <a>fi Suomalainen</a> Finnish | <a>fr français</a> French | <a>fy Frysk</a> Frisian | <a>gl Galego</a> Galician | <a>ka ქართველი</a> Georgian | <a>de Deutsch</a> German | <a>el Ελληνικά</a> Greek | <a>gu ગુજરાતી</a> Gujarati | <a>ht Kreyòl ayisyen</a> Haitian Creole | <a>ha Hausa</a> Hausa | <a>haw Ōlelo Hawaiʻi</a> Hawaiian | <a>he עִברִית</a> Hebrew | <a>hi हिन्दी</a> Hindi | <a>hmn Hmong</a> Hmong | <a>hu Magyar</a> Hungarian | <a>is Íslenska</a> Icelandic | <a>ig Igbo</a> Igbo | <a>id bahasa Indonesia</a> Icelandic | <a>ga Gaeilge</a> Irish | <a>it Italiana/Italiano</a> | <a>ja 日本語</a> Japanese | <a>jw Wong jawa</a> Javanese | <a>kn ಕನ್ನಡ</a> Kannada | <a>kk Қазақ</a> Kazakh | <a>km ខ្មែរ</a> Khmer | <a>rw Kinyarwanda</a> Kinyarwanda | <a>ko-south 韓國語</a> Korean (South) | <a>ko-north 문화어</a> Korean (North) (NOT YET TRANSLATED) | <a>ku Kurdî</a> Kurdish (Kurmanji) | <a>ky Кыргызча</a> Kyrgyz | <a>lo ລາວ</a> Lao | <a>la Latine</a> Latin | <a>lt Lietuvis</a> Lithuanian | <a>lb Lëtzebuergesch</a> Luxembourgish | <a>mk Македонски</a> Macedonian | <a>mg Malagasy</a> Malagasy | <a>ms Bahasa Melayu</a> Malay | <a>ml മലയാളം</a> Malayalam | <a>mt Malti</a> Maltese | <a>mi Maori</a> Maori | <a>mr मराठी</a> Marathi | <a>mn Монгол</a> Mongolian | <a>my မြန်မာ</a> Myanmar (Burmese) | <a>ne नेपाली</a> Nepali | <a>no norsk</a> Norwegian | <a>or ଓଡିଆ (ଓଡିଆ)</a> Odia (Oriya) | <a>ps پښتو</a> Pashto | <a>fa فارسی</a> |Persian <a>pl polski</a> Polish | <a>pt português</a> Portuguese | <a>pa ਪੰਜਾਬੀ</a> Punjabi | No languages available that start with the letter Q | <a>ro Română</a> Romanian | <a>ru русский</a> Russian | <a>sm Faasamoa</a> Samoan | <a>gd Gàidhlig na h-Alba</a> Scots Gaelic | <a>sr Српски</a> Serbian | <a>st Sesotho</a> Sesotho | <a>sn Shona</a> Shona | <a>sd سنڌي</a> Sindhi | <a>si සිංහල</a> Sinhala | <a>sk Slovák</a> Slovak | <a>sl Slovenščina</a> Slovenian | <a>so Soomaali</a> Somali | [<a>es en español</a> Spanish | <a>su Sundanis</a> Sundanese | <a>sw Kiswahili</a> Swahili | <a>sv Svenska</a> Swedish | <a>tg Тоҷикӣ</a> Tajik | <a>ta தமிழ்</a> Tamil | <a>tt Татар</a> Tatar | <a>te తెలుగు</a> Telugu | <a>th ไทย</a> Thai | <a>tr Türk</a> Turkish | <a>tk Türkmenler</a> Turkmen | <a>uk Український</a> Ukrainian | <a>ur اردو</a> Urdu | <a>ug ئۇيغۇر</a> Uyghur | <a>uz O'zbek</a> Uzbek | <a>vi Tiếng Việt</a> Vietnamese | <a>cy Cymraeg</a> Welsh | <a>xh isiXhosa</a> Xhosa | <a>yi יידיש</a> Yiddish | <a>yo Yoruba</a> Yoruba | <a>zu Zulu</a> Zulu ) Available in 110 languages (108 when not counting English and North Korean, as North Korean has not been translated yet <a>Read about it here</a>)
Translations in languages other than English are machine translated and are not yet accurate. No errors have been fixed yet as of March 21st 2021. Please report translation errors <a>here</a>. Make sure to backup your correction with sources and guide me, as I don't know languages other than English well (I plan on getting a translator eventually) please cite <a>wiktionary</a> and other sources in your report. Failing to do so will result in a rejection of the correction being published.
Note: due to limitations with GitHub's interpretation of markdown (and pretty much every other web-based interpretation of markdown) clicking these links will redirect you to a separate file on a separate page that isn't the intended page. You will be redirected to the <a>.github folder</a> of this project, where the README translations are hosted.
Translations are currently done with Bing translate and DeepL. Support for Google Translate translations is coming to a close due to privacy concerns.
Index
<a>00.0 - Top</a>
<blockquote>
<a>00.1 - Title</a>
<a>00.2 - Read this article in a different language</a>
<a>00.3 - Index</a>
</blockquote>
<a>01.0 - Description</a>
<a>02.0 - About</a>
<a>03.0 - Wiki</a>
<a>04.0 - History</a>
<blockquote>
<a>04.1 - Pre-history</a>
<a>04.2 - Alpha History</a>
<a>04.3 - Beta History</a>
<a>04.4 - Modern History</a>
</blockquote>
<a>05.0 - Copying</a>
<a>06.0 - Credits</a>
<a>07.0 - Installation</a>
<a>08.0 - Version history</a>
<a>09.0 - Version history</a>
<a>10.0 - Software status</a>
<a>11.0 - Sponsor info</a>
<a>12.0 - Contributers</a>
<a>13.0 - Issues</a>
<blockquote>
<a>13.1 - Current issues</a>
<a>13.2 - Past issues</a>
<a>13.3 - Past pull requests</a>
<a>13.4 - Active pull requests</a>
</blockquote>
<a>14.0 - Resources</a>
<a>15.0 - Contributing</a>
<a>16.0 - About README</a>
<a>17.0 - README Version history</a>
<a>18.0 - Footer</a>
<blockquote>
<a>18.9 - End of file</a>
</blockquote>
About
See above.
Wiki
<a>Click/tap here to view this projects Wiki</a>
If the project has been forked, the Wiki was likely removed. Luckily, I include an embedded version. You can view it <a>here</a>.
History
Write about this projects history here.
Pre-history
No pre-history to show for this project.
Alpha history
No Alpha history to show for this project.
Beta history
No Beta history to show for this project.
Modern history
No Modern history to show for this project.
Copying
View the copying license for this project <a>here</a> (if you haven't built the project yet with the makefile, here is the original link: <a>COPYINGL</a>
Please note that you also have to follow the rules of the GNU General Public License v3 (GPL3) which you can view <a>here</a>
Credits
View the credits file for this project and see the people who got together to make this project by <a>clicking/tapping here</a>
Installation
View the installation instructions file for this project <a>here</a>
Requirements: Read the instructions for more info, and get the latest up-to-date instructions <a>here</a>
Sponsor info
You can sponsor this project if you like, but please specify what you want to donate to. <a>See the funds you can donate to here</a>
You can view other sponsor info <a>here</a>
Try it out! The sponsor button is right up next to the watch/unwatch button.
Version history
<strong>Version history currently unavailable</strong>
<strong>No other versions listed</strong>
Software status
All of my works are free some restrictions. DRM (<strong>D</strong>igital <strong>R</strong>estrictions <strong>M</strong>anagement) is not present in any of my works.
This sticker is supported by the Free Software Foundation. I never intend to include DRM in my works.
I am using the abbreviation "Digital Restrictions Management" instead of the more known "Digital Rights Management" as the common way of addressing it is false, there are no rights with DRM. The spelling "Digital Restrictions Management" is more accurate, and is supported by <a>Richard M. Stallman (RMS)</a> and the <a>Free Software Foundation (FSF)</a>
This section is used to raise awareness for the problems with DRM, and also to protest it. DRM is defective by design and is a major threat to all computer users and software freedom.
Image credit: <a>defectivebydesign.org/drm-free/...</a>
Contributers
Currently, I am the only contributer. Contributing is allowed, as long as you follow the rules of the <a>CONTRIBUTING.md</a> file.
<blockquote>
<ul>
<li>
<ol>
<li><a>seanpm2001</a> - x commits (As of Yr, DoW, Month, DoM, at ##:## a/pm)</li>
</ol>
</li>
<li>
<ol>
<li>No other contributers.</li>
</ol>
</li>
</ul>
</blockquote>
Issues
Current issues
<ul>
<li>
None at the moment
</li>
<li>
No other current issues
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Past issues
<ul>
<li>
None at the moment
</li>
<li>
No other past issues
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Past pull requests
<ul>
<li>
None at the moment
</li>
<li>
No other past pull requests
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Active pull requests
<ul>
<li>
None at the moment
</li>
<li>
No other active pull requests
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Resources
Here are some other resources for this project:
<a>Project language file A</a>
<a>Join the discussion on GitHub</a>
No other resources at the moment.
Contributing
Contributing is allowed for this project, as long as you follow the rules of the <code>CONTRIBUTING.md</code> file.
<a>Click/tap here to view the contributing rules for this project</a>
About README
<strong>File type:</strong> <code>Markdown Document (*.md *.mkd *.markdown)</code>
<strong>File version:</strong> <code>0.1.6 (Monday, August 23rd 2021 at 6:37 pm)</code>
<strong>Line count (including blank lines and compiler line):</strong> <code>0,407</code>
README version history
Version 0.1 (Sunday, March 21st 2021 at 7:50 pm)
<blockquote>
Changes:
<ul>
<li>
Started the file
</li>
<li>
Added the title section
</li>
<li>
Added the index
</li>
<li>
Added the about section
</li>
<li>
Added the Wiki section
</li>
<li>
Added the version history section
</li>
<li>
Added the issues section.
</li>
<li>
Added the past issues section
</li>
<li>
Added the past pull requests section
</li>
<li>
Added the active pull requests section
</li>
<li>
Added the contributors section
</li>
<li>
Added the contributing section
</li>
<li>
Added the about README section
</li>
<li>
Added the README version history section
</li>
<li>
Added the resources section
</li>
<li>
Added a software status section, with a DRM free sticker and message
</li>
<li>
Added the sponsor info section
</li>
</ul>
</blockquote>
<strong>ITERATION 5</strong>
<blockquote>
<ul>
<li>
Updated the title section
</li>
<li>
Updated the index
</li>
<li>
Added the history section
</li>
<li>
Updated the file info section
</li>
<li>
Updated the file history section
</li>
</ul>
</blockquote>
<strong>ITERATION 6</strong>
<blockquote>
<ul>
<li>
Updated the title section
</li>
<li>
Fixed and update template links
</li>
<li>
Updated the index
</li>
<li>
Added the copying section
</li>
<li>
Added the credits section
</li>
<li>
Added the installation section
</li>
<li>
Updated the resources section
</li>
<li>
Updated the contributors section
</li>
<li>
Added the technical notes section
</li>
<li>
Updated the footer
</li>
<li>
Updated the file info section
</li>
<li>
Updated the file history section
</li>
<li>
No other changes in version 0.1
</li>
</ul>
</blockquote>
Version 1 (Coming soon)
<blockquote>
Changes:
<ul>
<li>
Coming soon
</li>
<li>
No other changes in version 1
</li>
</ul>
</blockquote>
Version 2 (Coming soon)
<blockquote>
Changes:
<ul>
<li>
Coming soon
</li>
<li>
No other changes in version 2
</li>
</ul>
</blockquote>
You have reached the end of the README file
( <a>Back to top</a> | <a>Exit to GitHub</a> | <a>Exit to Bing</a> | <a>Exit to DuckDuckGo</a> | <a>Exit to Ecosia</a> )
EOF
Contributors ✨
Thanks goes to these wonderful people (<a>emoji key</a>):
<a><b>Sean P. Myrick V19.1.7.2</b></a><a>💻</a> <a>📖</a> <a>📝</a> <a>🐛</a> <a>📦</a> <a>📆</a> <a>🛡️</a> <a>🚧</a> <a>🤔</a>
<a><b>All Contributors</b></a><a>📖</a>
This project follows the <a>all-contributors</a> specification. Contributions of any kind welcome! | []
|
https://avatars.githubusercontent.com/u/6396088?v=4 | zig-nanoid | andreburgaud/zig-nanoid | 2022-01-25T05:03:34Z | Nanoid implementation in Zig | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/andreburgaud/zig-nanoid/tags | MIT | [
"nanoid",
"zig"
]
| 22 | false | 2023-09-10T07:30:57Z | false | false | unknown | github | []
| zig-nanoid
Nanoid implementation in Zig
When I need a random ID, I commonly generate a <a>UUID</a> because the <a>UUID specification</a> is precise, and the specified algorithms supporting UUID are sound.
I realized that <strong>Nanoid</strong> was very popular among JavaScript aficionados. So, as a curiosity to understand the underlying algorithms, I decided to implement Nanoid in Zig, which I'm currently learning.
Code
The code includes the nanoid implementation in file <code>nanoid.zig</code>, and a command line <code>main.zig</code> demonstrating how to use the library.
Usage of the CLI
Help
<code>$ nanoid --help
Usage:
nanoid Generate a nanoid with the default size (21) and default alphabet
nanoid -s | --size <size> Generate a nanoid with a custom size and default alphabet
nanoid -a | --alphabet <alphabet> Generate a nanoid with a custom alphabet (requires the size)
nanoid -h | --help Display this help
nanoid -v | --version Print the version
Examples:
nanoid
nanoid -s 42
nanoid -s 42 -a 0123456789</code>
Default
<code>$ nanoid
bnX1GLQViedU3axkMeFH1</code>
Custom Size
<code>$ nanoid --size 42
AO6gpj98L1J6bNKx-CCAbUjU060yoX8YtE6ntZNmZK</code>
Custom Size and Alphabet
<code>$ nanoid --size 42 --alphabet 0123456789
523818966093355749724259496656326495868533</code>
Build
The build uses a <code>justfile</code> https://github.com/casey/just tested on Mac OS and Linux.
To build in debug mode:
<code>$ just build
...</code>
To build in release mode:
<code>$ just release
...</code>
Test
<code>$ just test
...</code>
References
I did not find any concrete specs similar to the UUID specs and referred to some of the existing implementations.
Implementations
<ul>
<li>https://github.com/ai/nanoid (MIT License)</li>
<li>https://github.com/matoous/go-nanoid (MIT License)</li>
<li>https://github.com/puyuan/py-nanoid (MIT License)</li>
</ul>
Other References
<ul>
<li><a>Why is NanoID Replacing UUID?</a></li>
</ul> | []
|
https://avatars.githubusercontent.com/u/11765286?v=4 | zig_regex | peterino2/zig_regex | 2021-11-05T20:16:00Z | A regex implementation. | integration | 0 | 3 | 0 | 3 | https://api.github.com/repos/peterino2/zig_regex/tags | - | [
"zig",
"zig-package"
]
| 13 | false | 2025-03-20T10:44:51Z | false | false | unknown | github | []
| Zig Regex
A fairly quick regex implementation done a while back for learning purposes, I'll just clean it up and put it out there.
This one is largely implemented with tagged unions and recursive descent rather than a state machine or a
byte gobbler so it shows you actually can write zig programs in a fairly functional manner.
In fact it's pretty damn nice for it.
You can test the library with
<code>zig
zig test gregex.zig</code>
Usecases can be found in the .zig file itself,
but here's a simple usecase.
```zig
var test_restr = "name: <em>(.</em>)\((.*)\)$";
<code>var find = try re_find_once(test_restr, "date: 2077-06-24 name: adam jensen (occupation: killa)\n", alloc);
defer find.deinit(); // find has an arraylist of regex objects, this should be de-initialized when out of scope.
print("{s}\n", .{ find.text }); // This will print out the entire string
// the result supports groups
print("find.groups.items[1] = '{s}':\n", .{find.groups.items[0].text});
print("find.groups.items[2] = '{s}':\n", .{find.groups.items[0].text});
</code>
```
in terms of sequences, a few of the most commonly supported sequences are supported.
<ul>
<li><code>*, +, ?</code> : capture mode operators, respectively; zero or more, one or more, zero or one</li>
<li><code>()</code> : create a match group (does not support nesting)</li>
<li><code>[]</code>: or match group (match any union of elements within)</li>
<li><code>a-z</code>: sequence range match</li>
<li>predefined semantic groups:<ul>
<li><code>\s</code> : whitespace (capital version is inverted)</li>
<li><code>\w</code> : alphanumeric</li>
<li><code>\d</code> : digits</li>
</ul>
</li>
<li><code>!</code>: Single term negation negates matches that are a single term. does not work on <code>()</code> groups or. but will work on or-groups.<ul>
<li>negative look-ahead is not supported.</li>
</ul>
</li>
</ul>
Note: this is the first thing I've ever actually written in zig so there's a few growing pains in visible in the code. | []
|
https://avatars.githubusercontent.com/u/2112697?v=4 | advent-of-code-2021 | scorphus/advent-of-code-2021 | 2021-12-01T06:47:07Z | ⚡ Solutions to Advent of Code 2021 🎄 | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/scorphus/advent-of-code-2021/tags | BSD-3-Clause | [
"advent-of-code",
"advent-of-code-2021",
"advent-of-code-2021-zig",
"zig"
]
| 102 | false | 2023-07-25T14:52:03Z | true | false | unknown | github | []
| :christmas_tree: Advent of Code 2021
Solutions to <a>Advent of Code 2021</a> in <a>Zig</a> :zap:
Motivations
<ul>
<li>Learn <a>Zig</a> from <em><a>scratch</a></em>, its tooling and ecosystem :zap:</li>
<li>Practice problem solving :sweat_smile:</li>
<li>Have fun :slightly_smiling_face:</li>
</ul>
License
Code in this repository is distributed under the terms of the BSD 3-Clause
License (BSD-3-Clause).
See <a>LICENSE</a> for details. | []
|
https://avatars.githubusercontent.com/u/11761863?v=4 | prett | theoparis/prett | 2021-05-16T00:36:09Z | Prettier shell commands | main | 2 | 3 | 0 | 3 | https://api.github.com/repos/theoparis/prett/tags | MIT | [
"cli",
"shell",
"zig"
]
| 74 | false | 2024-05-18T00:11:30Z | false | false | unknown | github | []
| prett 🚀
A prettifier for sh commands, inspired by <a>ptSh</a>.
Prequisites
<ul>
<li>A font that is capable of displaying nerd icons.</li>
<li>CMake, Make, And Git</li>
<li>A shell (eg.zsh, bash)</li>
<li>A ansi color-compatible terminal (eg. Alacritty).</li>
</ul>
Building
<code>bash
git clone --recurse-submodules https://github.com/creepinson/prett
cd prett
./compile.sh ~/bin # The path to copy the binary to, defaults to ~/bin</code>
Usage
Run <code>prett sub-command</code>.
Compatible Commands
<ul>
<li><code>ls</code></li>
</ul>
Shell Aliases
You can optionally alias the default commands in your shell to point to the corresponding prett commands.
See <a>aliases.sh</a>. | []
|
https://avatars.githubusercontent.com/u/145012?v=4 | zig-ksuid | toffaletti/zig-ksuid | 2021-11-26T08:52:03Z | zig implementation of ksuid | main | 0 | 3 | 0 | 3 | https://api.github.com/repos/toffaletti/zig-ksuid/tags | MIT | [
"ksuid",
"zig"
]
| 13 | false | 2024-10-08T06:38:43Z | true | false | unknown | github | []
| zig-ksuid
Zig implementation of <a>Segment.io's KSUID</a>. A mostly direct port of the original Go implementation https://github.com/segmentio/ksuid.
library usage
To generate a KSUID you must provide a <code>std.rand.Random</code>. In this example we are using the default cryptographically secure rng provided by the zig std library.
<code>zig
var secret_seed: [std.rand.DefaultCsprng.secret_seed_length]u8 = undefined;
std.crypto.random.bytes(&secret_seed);
var rand = std.rand.DefaultCsprng.init(secret_seed);
const k = KSUID.random(rand.random());
try stdout.print("{s}\n", .{k.fmt()});</code>
<code>zig
const k = try KSUID.parse("1srOrx2ZWZBpBUvZwXKQmoEYga2");</code>
command usage
Generate ksuid;
<code>./zig-out/bin/ksuid -n 5
21ZJr2CvT4q9YneIlvRsN2EH6MH
21ZJqz7FW1eU8jMUyuyoXRx2YIK
21ZJr2kAQeAiRqznp6UHyvvuk4k
21ZJqw99HJdsL9DhYBF1XwffcVp
21ZJr0QfjoyHkAwP8PL0GGs17e9</code>
Inspect a ksuid:
<code>./zig-out/bin/ksuid 0ujtsYcgvSTl8PAuAdqWYSMnLOv
0ujtsYcgvSTl8PAuAdqWYSMnLOv
2017-10-09 21:00:47 -0700 PDT
B5A1CD34B5F99D1154FB6853345C9735</code>
test coverage
To generate a coverage report with kcov:
<code>zig build test -Dcoverage
open kcov-output/index.html</code> | []
|
https://avatars.githubusercontent.com/u/1405645?v=4 | zloppy | jean-dao/zloppy | 2022-01-09T20:14:47Z | Sloppy Mode for Zig | master | 0 | 3 | 0 | 3 | https://api.github.com/repos/jean-dao/zloppy/tags | MIT | [
"zig",
"ziglang"
]
| 496 | false | 2025-04-22T19:04:37Z | true | false | unknown | github | []
| zloppy
Sloppy mode for Zig 0.12.0.
Tool to automatically silence compiler errors about unused variables and
unreachable code. Incidentally format code like <code>zig fmt</code> would do.
Status
Still in early development, expect bugs. Can be run on the stdlib and stage2
compiler (<code>lib/std</code> and <code>src</code> directories of zig repo) without false positives
nor bugs. There still may be some false negatives here and there.
Usage
Zloppy can be used where you would use <code>zig fmt</code>. For example, it can be used
instead of <code>zig fmt</code> in the vim plugin: just replace the command line used from
<code>zig fmt --stdin --ast-check</code> to <code>zloppy --stdin on</code>.
<code>zloppy on <files></code> will modify given files in place, adding statements and
comments as needed to supress errors about unused variables and unreachable
code. Can be re-applied multiple times on the same files.
Use <code>--experimental</code> to enable unused return values checks. This feature is
incomplete (only works for functions defined in the same file). It is guarded
behind a flag because it may lead to false positives with return values using
comptime features.
<code>zloppy off <files></code> will remove all modifications previously added with <code>zloppy on</code>.
Directories will be searched recursively. | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-licenses-text | nektro/zig-licenses-text | 2021-07-27T09:19:13Z | Full license text from https://spdx.org/licenses/. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/nektro/zig-licenses-text/tags | MIT | [
"zig",
"zig-package"
]
| 712 | false | 2025-05-21T20:33:38Z | true | false | unknown | github | []
| zig-licenses-text
<a></a>
<a></a>
<a></a>
<a></a>
Full license text from https://spdx.org/licenses/. | []
|
https://avatars.githubusercontent.com/u/143005?v=4 | zig-spsc-ring | cdolan/zig-spsc-ring | 2021-06-06T21:44:50Z | Single-producer single-consumer ring buffer | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/cdolan/zig-spsc-ring/tags | MIT | [
"lock-free",
"ring-buffer",
"spsc-queue",
"zig",
"ziglang"
]
| 5 | false | 2024-09-05T02:24:49Z | false | false | unknown | github | []
| zig-spsc-ring
Fast single-producer single-consumer wait-free ring buffer for Zig.
Usage
For efficient enqueuing and dequeuing, it is recommended that the ring size be
a power of two (i.e., 2^N), such as 8, 16, 32, 64, 256, 1024, 4096, etc...
If the size is not a power of two, a debug assertion will fail.
Example
```zig
const std = @import("std");
const Ring = @import("spsc_ring.zig").Ring;
pub fn main() !void {
var buf: [256]u64 = undefined;
var ring = Ring(u64).init(buf[0..]);
<code>var producer_thread = try std.Thread.spawn(.{}, producer, .{&ring});
var consumer_thread = try std.Thread.spawn(.{}, consumer, .{&ring});
producer_thread.join();
consumer_thread.join();
</code>
}
fn producer(ring: *Ring(u64)) void {
_ = ring.enqueue(42); // true - success. false - full buffer.
}
fn consumer(ring: *Ring(u64)) !void {
const stdout_file = std.io.getStdOut().writer();
var bw = std.io.bufferedWriter(stdout_file);
const stdout = bw.writer();
<code>while (true) {
if (ring.dequeue()) |answer| {
try stdout.print("answer = {}\n", .{answer});
try bw.flush();
return;
}
}
</code>
}
```
Zig
Tested on Zig 0.11.0-dev.1430+ce6de2df8
<ul>
<li>https://ziglang.org/</li>
<li>https://github.com/ziglang/zig</li>
<li>https://github.com/ziglang/zig/wiki/Community</li>
</ul>
License
MIT | []
|
https://avatars.githubusercontent.com/u/460371?v=4 | zupnp | wooky/zupnp | 2021-02-26T05:16:36Z | UPnP/DLNA library for Zig | master | 8 | 2 | 0 | 2 | https://api.github.com/repos/wooky/zupnp/tags | MIT | [
"upnp",
"webserver",
"xml",
"zig"
]
| 156 | false | 2023-07-07T15:42:46Z | true | false | unknown | github | []
| Zig UPnP Library (ZUPnP)
ZUPnP is a <a>Zig</a> library which features:
* UPnP/DLNA server
* Web server
* Web client
* XML parser
* Misc. utilities, such as UUID generator
This library is a high-level wrapper around the ubiquitous <a>pupnp</a> (Portable SDK for UPnP Devices, AKA libupnp) library, featuring a convenient API with some Zig-specific specialties thrown in.
Prerequisites
<ul>
<li>libupnp 1.14.x and libixml</li>
<li>You will also need these libraries during runtime, unless you statically link them to your application</li>
<li>Zig 0.8.x</li>
<li>libupnp-dev 1.14.x</li>
</ul>
When working with the library in your own code, you should add these lines to your build.zig's build() function:
<code>zig
const exe = b.addExecutable(...);
exe.addIncludeDir("/usr/include/upnp");
exe.linkLibC();
exe.linkSystemLibrary("upnp");
exe.linkSystemLibrary("ixml");
exe.addPackagePath("zupnp", "zupnp/src/lib.zig");
...</code>
Documentation
Detailed documentation is in progress. For now, check the <a>test</a> directory to see how some features work.
Examples
Some examples are included in the <a>samples</a> directory. Those include:
* <a>mediaserver</a> - serve contents to DLNA receivers
* <a>website</a> - basic demonstration of static content, GET, and POST requests
License
Licensed under the MIT license. | []
|
https://avatars.githubusercontent.com/u/19696698?v=4 | brainfuck | dvob/brainfuck | 2021-09-19T20:44:55Z | Brainfuck interpreters written in various languages | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/dvob/brainfuck/tags | - | [
"brainfuck",
"go",
"interpreter",
"python",
"rust",
"zig"
]
| 43 | false | 2025-03-23T16:14:19Z | false | false | unknown | github | []
| brainfuck
Brainfuck interpreters written in various languages:
<ul>
<li><a>rust</a></li>
<li><a>zig</a></li>
<li><a>go</a></li>
<li><a>python</a></li>
<li><a>c</a> </li>
<li><a>javascript</a></li>
<li><a>mojo</a></li>
</ul> | []
|
https://avatars.githubusercontent.com/u/473672?v=4 | wordle-cli | fabioarnold/wordle-cli | 2022-01-25T21:28:07Z | A wordle clone on the command line. | main | 0 | 2 | 1 | 2 | https://api.github.com/repos/fabioarnold/wordle-cli/tags | MIT | [
"wordle",
"zig"
]
| 9 | false | 2023-05-27T19:52:15Z | true | false | unknown | github | []
| wordle-cli
A wordle clone on the command line written in the <a>Zig programming language</a>.
Build instructions
Install Zig and run <code>zig build run</code>. | []
|
https://avatars.githubusercontent.com/u/145012?v=4 | zig-array-map | toffaletti/zig-array-map | 2021-06-06T01:45:07Z | ArrayMap data structure for Zig | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/toffaletti/zig-array-map/tags | MIT | [
"zig"
]
| 10 | false | 2024-10-25T08:34:47Z | true | false | unknown | github | []
| Zig ArrayMap
ArrayMap is a data structure that maps keys to values using an array of entries, optionally kept sorted by key. The contiguous layout in memory is cache friendly and can make ArrayMap a good choice for small amounts of data or data that is already sorted, written infrequently, but read many times.
<code>┌┬────────────┬┬────────────┬┬────────────┬~
││ Entry ││ Entry ││ Entry │~
│├────┬┬──────┤├────┬┬──────┤├────┬┬──────┤~
││Key ││Value ││Key ││Value ││Key ││Value │~
└┴────┴┴──────┴┴────┴┴──────┴┴────┴┴──────┴~</code> | []
|
https://avatars.githubusercontent.com/u/39132384?v=4 | allRGB | JoaoCostaIFG/allRGB | 2021-06-25T16:53:20Z | Convert PNG image files to PNG image files where all pixels are a different color from all others. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/JoaoCostaIFG/allRGB/tags | MIT | [
"allrgb",
"color-difference",
"octree",
"rgb",
"zig"
]
| 4,302 | false | 2022-07-22T00:38:14Z | true | false | unknown | github | []
| AllRGB
Convert an input PNG image file to an output PNG image file where every pixel is
a different color from all the others. It works with images of any aspect ratio,
but care needs to be taken to not use images with more than 16777216 pixels
(number of RGB colors).
The main interest of this program is to input images with 16777216 pixels (e.g.:
4096x4096 px) so we get an output with the different RGB colors. The idea came
from <a>allRGB.com</a>.
Compile
To compile the program, it is enough to just call:
<code>shell
zig build</code>
in the root directory of the project (no external dependencies needed).
Usage
The program takes the path to input image file as argument. It also accepts a
few optional arguments:
<ul>
<li><code>--no_random</code> - the pixels are evaluated from left to right, top to bottom,
instead of randomly.</li>
<li><code>--slow</code> - uses a slower, alternative color selection criterion for
conflicting colors (described below).</li>
<li><code>--do_check</code> - option useful for debugging. The program will perform a
self-check to determine if no colors have been used more than once.</li>
<li><code>--noise <int></code> - integer (%) that determines the amount of noise introduced
to the image. The default value is 10%.</li>
<li><code>-o <out.png></code> - Select name of the output file. The default is <code>out.png</code>.</li>
</ul>
Algorithm
Octree
The code uses an <a>octree</a> to represent
the RGB color space. This mean that the octree is 8 levels deep (excluding the
root node).
Color representation
Each node of the octree contains the number of unused colors in that node. Each
leaf of the tree represents a color. The color represented is obtained as
follows:
<ol>
<li>Take the ith bit from the R, G, and B components of a color.</li>
<li>With these 3 bits, we can obtain a 3-bit integer ([0, 7]), RiGiBi.</li>
<li>This integer is used to select the next child to explore in the tree.</li>
<li>We repeat this process 8 times: 8-bit RGB components; each iteration takes 1
bit from each.</li>
</ol>
e.g.:
```txt
RGB = #45152A
7 6 5 4 3 2 1 9
R: 0 1 0 0 0 1 0 1
G: 0 0 0 1 0 1 0 1
B: 0 0 1 0 1 0 1 0
i: 0 4 1 2 1 6 1 6
```
Color selection
We decrement the count of unused children colors for each node we pass. When we
attempt to choose a child-node that has no more colors available, we need to
choose a different neighbor. This choice can depend on the chosen criterion:
<ul>
<li>0 (default) - we use a lookup table:</li>
</ul>
<code>txt
[
[ 1, 4, 5, 2, 3, 6, 7 ],
[ 0, 5, 4, 3, 2, 7, 6 ],
[ 3, 6, 7, 0, 1, 4, 5 ],
[ 2, 7, 6, 1, 0, 5, 4 ],
[ 5, 0, 1, 6, 7, 2, 3 ],
[ 4, 1, 0, 7, 6, 3, 2 ],
[ 7, 2, 3, 4, 5, 0, 1 ],
[ 6, 3, 2, 5, 4, 1, 0 ],
]</code>
This criterion is the fastest and usually generates images that resemble a sepia
tone.
<ul>
<li>1 (<code>--slow</code>) - we use a
<a>weighted mean</a> to find which neighbor
potentially allows the most similar color (based on distances). This criterion
is noticeably slower than the previous one, but is faster than converting the
colors to another color space (e.g.: CIELAB) and allows us keep working in RGB
only (stay in theme). Images produced are 'more vibrant' when using this
criterion.</li>
</ul>
Examples
<ul>
<li>Image</li>
</ul>
<ul>
<li>Image produced using the program's default options</li>
</ul>
<ul>
<li>Image produced using the <code>--slow</code> option</li>
</ul>
<ul>
<li>Image produced without introducing noise to the image</li>
</ul>
LodePNG
<a>LodePNG</a> is used to both <strong>read</strong> and
<strong>write</strong> PNG image files.
Bibliography
<ul>
<li><a>Octree to represent RGB space</a></li>
<li><a>Color quantization using an octree</a></li>
<li><a>Color quantization for dithering</a></li>
<li><a>Source for the lookup table</a></li>
<li><a>Source for the formula for the RGB color distance</a></li>
</ul>
License
Unless stated otherwise, all the source code files included in this repository
are licensed under an <a>MIT license</a> present in
<a>this file</a>. | []
|
https://avatars.githubusercontent.com/u/14790226?v=4 | zline | chivay/zline | 2021-10-03T11:41:20Z | readline replacement for Zig | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/chivay/zline/tags | MIT | [
"library",
"readline",
"terminal",
"zig"
]
| 10 | false | 2022-09-14T02:06:52Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/9347096?v=4 | mimalloc-zig | massivelivefun/mimalloc-zig | 2021-09-30T03:47:29Z | A Zig implementation of Microsoft's mimalloc. | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/massivelivefun/mimalloc-zig/tags | MIT | [
"library",
"memory-allocator",
"zig"
]
| 32 | false | 2024-09-25T04:17:57Z | true | false | unknown | github | []
| mimalloc-zig
A Zig implementation of Microsoft's mimalloc.
What is mimalloc-zig?
TBD
Installation
TBD
Prerequisties
TBD
Contributing
TBD
License
Copyright © 2022 - Present, The Repo's Contributers.
This project is licensed with the MIT license. | []
|
https://avatars.githubusercontent.com/u/146390816?v=4 | opendynamics-engine | allyourcodebase/opendynamics-engine | 2021-09-06T14:11:20Z | Zig ODE sdk | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/allyourcodebase/opendynamics-engine/tags | - | [
"ode",
"open-dynamics-engine",
"zig",
"zig-package",
"ziglang"
]
| 8 | false | 2025-04-15T18:38:45Z | true | false | unknown | github | []
| zig-ode | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | ghr | nektro/ghr | 2021-08-26T03:10:35Z | Create GitHub releases and upload artifacts from the terminal. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/nektro/ghr/tags | MIT | [
"github",
"release-automation",
"zig"
]
| 47 | false | 2025-05-13T19:42:43Z | true | false | unknown | github | []
| ghr
<a></a>
Create GitHub releases and upload artifacts from the terminal.
Based on the popular https://github.com/tcnksm/ghr, brought to the world of Zig.
Usage
<code>sh
$ ghr [option] TAG PATH</code>
Options
<code>sh
-t TOKEN # *Set Github API Token
-u USERNAME # *Set Github username
-r REPO # *Set repository name
-c COMMIT # Set target commitish, branch or commit SHA
-n TITLE # Set release title
-b BODY # Set text describing the contents of the release
-draft # Release as draft (Unpublish)
-prerelease # Create prerelease
TAG # *Name of the git tag to create
PATH # *Directory that contains the artifacts to upload</code>
Installation
With <a>Zigmod</a>
<code>sh
$ zigmod aq install 1/nektro/ghr</code>
From Source
<code>zigmod fetch
zig build</code>
Built With
<ul>
<li>Zig 0.13.0</li>
</ul>
License
MIT | []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | b2pw | x13a/b2pw | 2021-11-27T04:48:45Z | Convert bytes to password. | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/x13a/b2pw/tags | GPL-3.0 | [
"zig",
"zig-lang"
]
| 22 | false | 2024-03-08T02:50:22Z | true | false | unknown | github | []
| b2pw
Convert bytes to password.
Main purpose is to convert files to passwords. You can take any file and convert it
to password up to 64 chars long. First we make hash of it using <code>blake2b</code>, than
map each result byte to our alphabet. On the same file you always get the same password.
Installation
<code>sh
$ make
$ make install</code>
or
<code>sh
$ brew tap x13a/tap
$ brew install x13a/tap/b2pw</code>
Usage
```text
b2pw [-hV] [-l NUM] [-a STR] [-k STR] [-c STR] [-n NUM]
[-h] * Print help and exit
[-V] * Print version and exit
[-l] * Length of password (default: 32)
[-a] * Alphabet (default: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789)
[-k] * Key (default: null)
[-c] * Additional chars (default: "")
[-n] * Number of bytes to read (default: 0 = all)
```
Example
<code>sh
~
❯ echo -n "test1" | b2pw
RQ3sDNrPzzkiVLYsqRzsnQTkgbK4cm0U
~
❯ echo -n "test1" | b2pw
RQ3sDNrPzzkiVLYsqRzsnQTkgbK4cm0U
~
❯ echo -n "test2" | b2pw
KS4qquoEFhN4XJiECDcQZxJXca6ZrKCN</code> | []
|
https://avatars.githubusercontent.com/u/9347096?v=4 | qpzig | massivelivefun/qpzig | 2021-12-06T09:11:22Z | A Zig implementation of Quantum Leaps' QP (Quantum Platform) Real-Time Embedded Frameworks (RTEFs). | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/massivelivefun/qpzig/tags | MIT | [
"actor",
"actor-model",
"event-driven",
"framework",
"fsm",
"qp",
"rtos",
"state-machines",
"zig"
]
| 14 | false | 2024-10-28T04:42:44Z | true | false | unknown | github | []
| qpzig
A Zig implementation of Quantum Leaps' QP (Quantum Platform) Real-Time Embedded Frameworks (RTEFs). | []
|
https://avatars.githubusercontent.com/u/65933340?v=4 | SNU_2D_ProgrammingTools_IDE_Zig | seanpm2001/SNU_2D_ProgrammingTools_IDE_Zig | 2021-11-29T22:27:17Z | The Zig Programming language IDE submodule for SNU Programming Tools (2D Mode) | main | 0 | 2 | 2 | 2 | https://api.github.com/repos/seanpm2001/SNU_2D_ProgrammingTools_IDE_Zig/tags | GPL-3.0 | [
"gpl3",
"gplv3",
"ide",
"md",
"programming",
"snu",
"snu-2d",
"snu-2d-programming-tools",
"snu-2d-programmingtools",
"snu-development",
"snu-programming-tools",
"snu2d-programmingtools",
"snu2dprogrammingtools",
"txt",
"web",
"web-ide",
"zig",
"zig-language",
"ziglang",
"zir"
]
| 972 | false | 2022-11-11T02:32:46Z | false | false | unknown | github | []
|
SNU-2D-ProgrammingTools-IDE-
By:
<a>Seanpm2001</a> / <a>SNU Programming Tools</a>, Et; Al.
Top
<code>README.md</code>
Read this article in a different language
<em>Read this description in a different language:</em>
<strong>Current language is:</strong> <code>English (US)</code> <em>(translations may need to be corrected to fix English replacing the correct language)</em>
[Click/tap here to expand/collapse the language switcher list]
_🌐 List of languages_
( [af Afrikaans](/.github/README_AF.md) Afrikaans | [sq Shqiptare](/.github/README_SQ.md) Albanian | [am አማርኛ](/.github/README_AM.md) Amharic | [ar عربى](/.github/README_AR.md) Arabic | [hy հայերեն](/.github/README_HY.md) Armenian | [az Azərbaycan dili](/.github/README_AZ.md) Azerbaijani | [eu Euskara](/.github/README_EU.md) Basque | [be Беларуская](/.github/README_BE.md) Belarusian | [bn বাংলা](/.github/README_BN.md) Bengali | [bs Bosanski](/.github/README_BS.md) Bosnian | [bg български](/.github/README_BG.md) Bulgarian | [ca Català](/.github/README_CA.md) Catalan | [ceb Sugbuanon](/.github/README_CEB.md) Cebuano | [ny Chichewa](/.github/README_NY.md) Chichewa | [zh-CN 简体中文](/.github/README_ZH-CN.md) Chinese (Simplified) | [zh-t 中國傳統的）](/.github/README_ZH-T.md) Chinese (Traditional) | [co Corsu](/.github/README_CO.md) Corsican | [hr Hrvatski](/.github/README_HR.md) Croatian | [cs čeština](/.github/README_CS.md) Czech | [da dansk](README_DA.md) Danish | [nl Nederlands](/.github/README_NL.md) Dutch | [**en-us English**](/.github/README.md) English | [EO Esperanto](/.github/README_EO.md) Esperanto | [et Eestlane](/.github/README_ET.md) Estonian | [tl Pilipino](/.github/README_TL.md) Filipino | [fi Suomalainen](/.github/README_FI.md) Finnish | [fr français](/.github/README_FR.md) French | [fy Frysk](/.github/README_FY.md) Frisian | [gl Galego](/.github/README_GL.md) Galician | [ka ქართველი](/.github/README_KA) Georgian | [de Deutsch](/.github/README_DE.md) German | [el Ελληνικά](/.github/README_EL.md) Greek | [gu ગુજરાતી](/.github/README_GU.md) Gujarati | [ht Kreyòl ayisyen](/.github/README_HT.md) Haitian Creole | [ha Hausa](/.github/README_HA.md) Hausa | [haw Ōlelo Hawaiʻi](/.github/README_HAW.md) Hawaiian | [he עִברִית](/.github/README_HE.md) Hebrew | [hi हिन्दी](/.github/README_HI.md) Hindi | [hmn Hmong](/.github/README_HMN.md) Hmong | [hu Magyar](/.github/README_HU.md) Hungarian | [is Íslenska](/.github/README_IS.md) Icelandic | [ig Igbo](/.github/README_IG.md) Igbo | [id bahasa Indonesia](/.github/README_ID.md) Icelandic | [ga Gaeilge](/.github/README_GA.md) Irish | [it Italiana/Italiano](/.github/README_IT.md) | [ja 日本語](/.github/README_JA.md) Japanese | [jw Wong jawa](/.github/README_JW.md) Javanese | [kn ಕನ್ನಡ](/.github/README_KN.md) Kannada | [kk Қазақ](/.github/README_KK.md) Kazakh | [km ខ្មែរ](/.github/README_KM.md) Khmer | [rw Kinyarwanda](/.github/README_RW.md) Kinyarwanda | [ko-south 韓國語](/.github/README_KO_SOUTH.md) Korean (South) | [ko-north 문화어](README_KO_NORTH.md) Korean (North) (NOT YET TRANSLATED) | [ku Kurdî](/.github/README_KU.md) Kurdish (Kurmanji) | [ky Кыргызча](/.github/README_KY.md) Kyrgyz | [lo ລາວ](/.github/README_LO.md) Lao | [la Latine](/.github/README_LA.md) Latin | [lt Lietuvis](/.github/README_LT.md) Lithuanian | [lb Lëtzebuergesch](/.github/README_LB.md) Luxembourgish | [mk Македонски](/.github/README_MK.md) Macedonian | [mg Malagasy](/.github/README_MG.md) Malagasy | [ms Bahasa Melayu](/.github/README_MS.md) Malay | [ml മലയാളം](/.github/README_ML.md) Malayalam | [mt Malti](/.github/README_MT.md) Maltese | [mi Maori](/.github/README_MI.md) Maori | [mr मराठी](/.github/README_MR.md) Marathi | [mn Монгол](/.github/README_MN.md) Mongolian | [my မြန်မာ](/.github/README_MY.md) Myanmar (Burmese) | [ne नेपाली](/.github/README_NE.md) Nepali | [no norsk](/.github/README_NO.md) Norwegian | [or ଓଡିଆ (ଓଡିଆ)](/.github/README_OR.md) Odia (Oriya) | [ps پښتو](/.github/README_PS.md) Pashto | [fa فارسی](/.github/README_FA.md) |Persian [pl polski](/.github/README_PL.md) Polish | [pt português](/.github/README_PT.md) Portuguese | [pa ਪੰਜਾਬੀ](/.github/README_PA.md) Punjabi | No languages available that start with the letter Q | [ro Română](/.github/README_RO.md) Romanian | [ru русский](/.github/README_RU.md) Russian | [sm Faasamoa](/.github/README_SM.md) Samoan | [gd Gàidhlig na h-Alba](/.github/README_GD.md) Scots Gaelic | [sr Српски](/.github/README_SR.md) Serbian | [st Sesotho](/.github/README_ST.md) Sesotho | [sn Shona](/.github/README_SN.md) Shona | [sd سنڌي](/.github/README_SD.md) Sindhi | [si සිංහල](/.github/README_SI.md) Sinhala | [sk Slovák](/.github/README_SK.md) Slovak | [sl Slovenščina](/.github/README_SL.md) Slovenian | [so Soomaali](/.github/README_SO.md) Somali | [[es en español](/.github/README_ES.md) Spanish | [su Sundanis](/.github/README_SU.md) Sundanese | [sw Kiswahili](/.github/README_SW.md) Swahili | [sv Svenska](/.github/README_SV.md) Swedish | [tg Тоҷикӣ](/.github/README_TG.md) Tajik | [ta தமிழ்](/.github/README_TA.md) Tamil | [tt Татар](/.github/README_TT.md) Tatar | [te తెలుగు](/.github/README_TE.md) Telugu | [th ไทย](/.github/README_TH.md) Thai | [tr Türk](/.github/README_TR.md) Turkish | [tk Türkmenler](/.github/README_TK.md) Turkmen | [uk Український](/.github/README_UK.md) Ukrainian | [ur اردو](/.github/README_UR.md) Urdu | [ug ئۇيغۇر](/.github/README_UG.md) Uyghur | [uz O'zbek](/.github/README_UZ.md) Uzbek | [vi Tiếng Việt](/.github/README_VI.md) Vietnamese | [cy Cymraeg](/.github/README_CY.md) Welsh | [xh isiXhosa](/.github/README_XH.md) Xhosa | [yi יידיש](/.github/README_YI.md) Yiddish | [yo Yoruba](/.github/README_YO.md) Yoruba | [zu Zulu](/.github/README_ZU.md) Zulu ) Available in 110 languages (108 when not counting English and North Korean, as North Korean has not been translated yet [Read about it here](/OldVersions/Korean(North)/README.md))
Translations in languages other than English are machine translated and are not yet accurate. No errors have been fixed yet as of February 5th 2021. Please report translation errors <a>here</a> make sure to backup your correction with sources and guide me, as I don't know languages other than English well (I plan on getting a translator eventually) please cite <a>wiktionary</a> and other sources in your report. Failing to do so will result in a rejection of the correction being published.
Note: due to limitations with GitHub's interpretation of markdown (and pretty much every other web-based interpretation of markdown) clicking these links will redirect you to a separate file on a separate page that isn't my GitHub profile page. You will be redirected to the <a>seanpm2001/seanpm2001 repository</a>, where the README is hosted.
Translations are done with Google Translate due to limited or no support for the languages I need in other translation services like DeepL and Bing Translate. For some reason, the formatting (links, dividers, bolding, italics, etc.) is messed up in various translations. It is tedious to fix, and I do not know how to fix these issues in languages with non-latin characters, and right to left languages (like Arabic) extra help is needed in fixing these issues
Index
<a>00.0 - Top</a>
<blockquote>
<a>00.1 - Title</a>
<a>00.2 - Read this article in a different language</a>
<a>00.3 - Index</a>
</blockquote>
<a>01.0 - Description</a>
<a>02.0 - About</a>
<a>03.0 - Wiki</a>
<a>04.0 - History</a>
<blockquote>
<a>04.1 - Pre-history</a>
<a>04.2 - Alpha History</a>
<a>04.3 - Beta History</a>
<a>04.4 - Modern History</a>
</blockquote>
<a>05.0 - Copying</a>
<a>06.0 - Credits</a>
<a>07.0 - Installation</a>
<a>08.0 - Version history</a>
<a>09.0 - Software status</a>
<a>10.0 - Sponsor info</a>
<a>11.0 - Contributers</a>
<a>12.0 - Issues</a>
<blockquote>
<a>12.1 - Current issues</a>
<a>12.2 - Past issues</a>
<a>12.3 - Past pull requests</a>
<a>12.4 - Active pull requests</a>
</blockquote>
<a>13.0 - Resources</a>
<a>14.0 - Contributing</a>
<a>15.0 - About README</a>
<a>16.0 - README Version history</a>
<a>17.0 - Footer</a>
<blockquote>
<a>17.9 - End of file</a>
</blockquote>
SNU_2D_ProgrammingTools_IDE_
The Programming language IDE submodule for SNU Programming Tools (2D Mode)
About
See above. This repository is the IDE for that comes with SNUs programming tool set.
Wiki
<a>Click/tap here to view this projects Wiki</a>
If the project has been forked, the Wiki was likely removed. Luckily, I include an embedded version. You can view it <a>here</a>.
History
Write about this projects history here.
Pre-history
No pre-history to show for this project.
Alpha history
No Alpha history to show for this project.
Beta history
No Beta history to show for this project.
Modern history
No Modern history to show for this project.
Copying
View the copying license for this project <a>here</a> (if you haven't built the project yet with the makefile, here is the original link: <a>COPYINGL</a>
Please note that you also have to follow the rules of the GNU General Public License v3 (GPL3) which you can view <a>here</a>
Credits
View the credits file for this project and see the people who got together to make this project by <a>clicking/tapping here</a>
Installation
View the installation instructions file for this project <a>here</a>
Requirements: Read the instructions for more info, and get the latest up-to-date instructions <a>here</a>
Sponsor info
You can sponsor this project if you like, but please specify what you want to donate to. <a>See the funds you can donate to here</a>
You can view other sponsor info <a>here</a>
Try it out! The sponsor button is right up next to the watch/unwatch button.
Version history
<strong>Version history currently unavailable</strong>
<strong>No other versions listed</strong>
Software status
All of my works are free some restrictions. DRM (<strong>D</strong>igital <strong>R</strong>estrictions <strong>M</strong>anagement) is not present in any of my works.
This sticker is supported by the Free Software Foundation. I never intend to include DRM in my works.
I am ussing the abbreviation "Digital Restrictions Management" instead of the more known "Digital Rights Management" as the common way of addressing it is false, there are no rights with DRM. The spelling "Digital Restrictions Management" is more accurate, and is supported by <a>Richard M. Stallman (RMS)</a> and the <a>Free Software Foundation (FSF)</a>
This section is used to raise awareness for the problems with DRM, and also to protest it. DRM is defective by design and is a major threat to all computer users and software freedom.
Image credit: <a>defectivebydesign.org/drm-free/...</a>
Contributers
Currently, I am the only contributer. Contributing is allowed, as long as you follow the rules of the <a>CONTRIBUTING.md</a> file.
<blockquote>
<ul>
<li>
<ol>
<li><a>seanpm2001</a> - x commits (As of 2021, date, at xx:xx pm)</li>
</ol>
</li>
<li>
<ol>
<li>No other contributers.</li>
</ol>
</li>
</ul>
</blockquote>
Issues
Current issues
<ul>
<li>
None at the moment
</li>
<li>
No other current issues
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Past issues
<ul>
<li>
None at the moment
</li>
<li>
No other past issues
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Past pull requests
<ul>
<li>
None at the moment
</li>
<li>
No other past pull requests
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Active pull requests
<ul>
<li>
None at the moment
</li>
<li>
No other active pull requests
</li>
</ul>
If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images <a>here</a>
<a>Read the privacy policy on issue archival here</a>
<strong>TL;DR</strong>
I archive my own issues. Your issue won't be archived unless you request it to be archived.
Resources
Here are some other resources for this project:
<a>Project language file A</a>)
<a>Join the discussion on GitHub</a>
No other resources at the moment.
Contributing
Contributing is allowed for this project, as long as you follow the rules of the <code>CONTRIBUTING.md</code> file.
<a>Click/tap here to view the contributing rules for this project</a>
About README
<strong>File type:</strong> <code>Markdown document (*.md)</code>
<strong>File version:</strong> <code>1 (date)</code>
<strong>Line count:</strong> <code>0,415</code>
README version history
Version 1 (Date)
<blockquote>
Changes:
<ul>
<li>
Started the file
</li>
<li>
Added the title section
</li>
<li>
Added the index
</li>
<li>
Added the about section
</li>
<li>
Added the Wiki section
</li>
<li>
Added the version history section
</li>
<li>
Added the issues section.
</li>
<li>
Added the past issues section
</li>
<li>
Added the past pull requests section
</li>
<li>
Added the active pull requests section
</li>
<li>
Added the contributors section
</li>
<li>
Added the contributing section
</li>
<li>
Added the about README section
</li>
<li>
Added the README version history section
</li>
<li>
Added the resources section
</li>
<li>
Added a software status section, with a DRM free sticker and message
</li>
<li>
Added the sponsor info section
</li>
</ul>
</blockquote>
<strong>ITERATION 5</strong>
<blockquote>
<ul>
<li>
Updated the title section
</li>
<li>
Updated the index
</li>
<li>
Added the history section
</li>
<li>
Updated the file info section
</li>
<li>
Updated the file history section
</li>
<li>
Updated the footer
</li>
</ul>
</blockquote>
<strong>ITERATION 6</strong>
<blockquote>
<ul>
<li>
Updated the title section
</li>
<li>
Fixed and update template links
</li>
<li>
Updated the index
</li>
<li>
Added the copying section
</li>
<li>
Added the credits section
</li>
<li>
Added the installation section
</li>
<li>
Updated the resources section
</li>
<li>
Updated the contributors section
</li>
<li>
Added the technical notes section
</li>
<li>
Updated the footer
</li>
<li>
Updated the file info section
</li>
<li>
Updated the file history section
</li>
<li>
No other changes in version 1
</li>
</ul>
</blockquote>
Version 2 (Coming soon)
<blockquote>
Changes:
<ul>
<li>
Coming soon
</li>
<li>
No other changes in version 2
</li>
</ul>
</blockquote>
You have reached the end of the README file
( <a>Back to top</a> | <a>Exit to GitHub</a> | <a>Exit to Bing</a> | <a>Exit to DuckDuckGo</a> | <a>Exit to Ecosia</a> )
EOF
| []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | balock | x13a/balock | 2021-02-13T02:04:29Z | Bruteforce OEM and NCK codes for Balong V7R11. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/x13a/balock/tags | GPL-3.0 | [
"balong",
"bruteforce",
"huawei",
"zig",
"zig-lang"
]
| 31 | false | 2024-02-14T01:37:09Z | true | false | unknown | github | []
| balock
Bruteforce OEM and NCK codes for Balong V7R11.
Huawei E5573<strong>, E5577</strong>, E8372h, E3372h..
Credits to rust3028, Decker, forth32..
Installation
<code>sh
$ make
$ make install</code>
or
<code>sh
$ brew tap x13a/tap
$ brew install x13a/tap/balock</code>
Usage
```text
balock [-h|V]
[-h] * Print help and exit
[-V] * Print version and exit
```
AT
OEM:
<code>text
$ AT^NVRDEX=50502,0,128</code>
NCK:
<code>text
$ AT^NVRDEX=50503,0,128</code> | []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | zig-sort | x13a/zig-sort | 2021-05-07T19:33:15Z | Some sort algorithms in zig. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/x13a/zig-sort/tags | 0BSD | [
"algorithms",
"sort",
"zig",
"zig-lang"
]
| 8 | false | 2023-09-06T18:20:33Z | true | false | unknown | github | []
| zig-sort
Some sort algorithms in <a>zig</a>.
Types
<ul>
<li><a>Heap</a></li>
<li><a>Insertion</a></li>
<li><a>Merge</a></li>
<li><a>Quick</a></li>
<li><a>Selection</a></li>
<li><a>Shell</a></li>
</ul> | []
|
https://avatars.githubusercontent.com/u/200686?v=4 | lc3-zig | deckarep/lc3-zig | 2022-02-02T01:33:49Z | The LC3 virtual machine implemented in Zig. | main | 0 | 2 | 0 | 2 | https://api.github.com/repos/deckarep/lc3-zig/tags | MIT | [
"assembly",
"bytecode-interpreter",
"lc3",
"lc3-vm",
"virtual-machine",
"zig",
"ziglang"
]
| 8 | false | 2024-12-27T04:31:47Z | true | false | unknown | github | []
| lc3-zig
The LC3 virtual machine implemented in Zig.
Hold on to your horses, not fully implemented. | []
|
https://avatars.githubusercontent.com/u/20849197?v=4 | zig-debian | NickHastings/zig-debian | 2022-01-19T00:42:44Z | Debian package for zig programming language | main | 1 | 2 | 0 | 2 | https://api.github.com/repos/NickHastings/zig-debian/tags | NOASSERTION | [
"debian-package",
"zig"
]
| 128 | false | 2024-07-15T04:54:18Z | false | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/197274?v=4 | zig-raytracer | jhenninger/zig-raytracer | 2021-07-03T13:12:58Z | Ray tracer written in Zig based on "Ray Tracing in One Weekend" | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/jhenninger/zig-raytracer/tags | - | [
"raytracer",
"raytracing",
"raytracing-in-one-weekend",
"raytracing-one-weekend",
"zig"
]
| 396 | false | 2024-11-24T11:37:03Z | true | false | unknown | github | []
| Zig Ray Tracer
Multi-threaded ray tracer written in <a>Zig</a>.
Based on a probably now outdated version of <a>Ray Tracing in One Weekend</a>. | []
|
https://avatars.githubusercontent.com/u/22225222?v=4 | zitrus | arguablykomodo/zitrus | 2022-01-24T21:19:30Z | A set of opinionated system information fetchers written in Zig, for use in lemonbar. | master | 0 | 2 | 0 | 2 | https://api.github.com/repos/arguablykomodo/zitrus/tags | GPL-3.0 | [
"lemonbar",
"zig"
]
| 65 | false | 2024-05-31T19:21:15Z | true | false | unknown | github | []
| Zitrus
A set of opinionated system information fetchers written in Zig, for use in
<a>lemonbar</a>.
Building
Requires Zig 0.11.0.
<code>zig build</code> will build all the fetchers, <code>zig build <i>name</i></code>
will build just the specified fetcher.
Fetchers
<code>cpu</code>
Displays CPU utilization as a percentage alongside per-core bars.
<b>zitrus-cpu</b> [<i>interval</i>] [<i>color</i> ...]
<ul>
<li><code>interval</code>: Time between updates, in milliseconds. Defaults to 1000. Shorter
intervals will lead to faster updates but less useful measurements.</li>
<li><code>color</code>: RRGGBB formatted color. Bars will use these colors blended
first-to-last based on percentage. Bars will be colorless if not present.</li>
</ul>
<code>ram</code>
<b>zitrus-ram</b> [<i>interval</i>] [<i>color</i> ...]
Displays RAM usage as total percentage alongside a colored bar.
<ul>
<li><code>interval</code>: Time between updates, in milliseconds. Defaults to 1000.</li>
<li><code>color</code>: RRGGBB formatted color. Bar will use these colors blended
first-to-last based on percentage. Bar will be colorless if not present.</li>
</ul>
<code>net</code>
Displays download/upload speed of all interfaces (excluding loopback).
<b>zitrus-net</b> <b>down</b>|<b>up</b> [<i>interval</i>]
<ul>
<li><code>interval</code>: Time between updates, in milliseconds. Defaults to 1000. Shorter
intervals will lead to faster updates but less useful measurements.</li>
</ul>
<code>bspwm</code>
Displays list of current occupied bspwm desktops, with the focused desktop
highlighted. Requires <code>bspc</code> to be on <code>$PATH</code>.
<b>zitrus-bspwm</b> <i>monitor_name</i> [<i>focus_color</i>]
<ul>
<li><code>monitor_name</code>: Name of monitor whose desktops will be displayed. <code>bspc query
-M --names</code> can be useful to figure out the name.</li>
<li><code>focus_color</code>: Color used to highlight focused desktop.</li>
</ul>
<code>mpd</code>
Displays current track artist, title, duration and elapsed time. Will display
filename if track has no title.
<b>zitrus-mpd</b>
<code>pulseaudio</code>
Displays volume of default audio sink as a percentage. Requires linking with
<code>libc</code> and <code>libpulse</code>.
<b>zitrus-pulseaudio</b> | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-flag | nektro/zig-flag | 2021-09-11T08:31:50Z | Config management for Zig. | master | 0 | 2 | 1 | 2 | https://api.github.com/repos/nektro/zig-flag/tags | MIT | [
"zig",
"zig-package"
]
| 17 | false | 2025-05-21T20:33:34Z | true | false | unknown | github | []
| zig-flag
<a></a>
<a></a>
<a></a>
<a></a>
Config management for Zig.
Ideal if you would like to define flags in multiple modules or multiplex intake between CLI flags or environement variables. | []
|
https://avatars.githubusercontent.com/u/42384293?v=4 | zbfi | prajwalch/zbfi | 2021-12-11T14:11:34Z | BrainFuck 🤖 language interpreter written in Zig | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/prajwalch/zbfi/tags | MIT | [
"brainfuck",
"brainfuck-interpreter",
"interpreter",
"zig",
"zig-lang",
"ziglang"
]
| 73 | false | 2022-12-14T23:59:12Z | true | false | unknown | github | []
| zbfi
zbfi is a BrainFuck programming language interpreter written in zig.
It is written only to learn zig for myself but you can experiment
with the code however you like.
Building
To build the project you only need to have a <a>zig compiler - v0.9.0</a>
All the install instructions are there, so download and install it according to the instructions then follow the below steps.
<ol>
<li>Clone it with <code>git clone --recursive https://github.com/PrajwalCH/zbfi</code></li>
<li>Change directory to zbfi</li>
<li>Run <code>zig build -Drelease-safe=true</code> to build it.</li>
<li>And at last run <code>./zig-out/bin/zbfi</code> for interactive mode or <code>./zig-out/bin -f <file name></code> to run source file</li>
</ol> | []
|
https://avatars.githubusercontent.com/u/1007628?v=4 | puzzles | jcmoyer/puzzles | 2021-11-11T02:23:46Z | collection of solutions for various programming puzzles | master | 1 | 1 | 0 | 1 | https://api.github.com/repos/jcmoyer/puzzles/tags | - | [
"advent-of-code",
"cpp",
"zig"
]
| 1,259 | false | 2024-12-30T19:32:27Z | false | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-licenses | nektro/zig-licenses | 2021-02-15T01:59:38Z | generated data from https://spdx.org/licenses/. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/nektro/zig-licenses/tags | MIT | [
"zig",
"zig-package"
]
| 52 | false | 2025-05-21T20:33:31Z | true | false | unknown | github | []
| zig-licenses
<a></a>
<a></a>
<a></a>
<a></a>
generated data from https://spdx.org/licenses/.
includes extra declarations for OSI approved licenses.
includes extra declarations for https://blueoakcouncil.org/list classes. | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-fmt-valueliteral | nektro/zig-fmt-valueliteral | 2021-05-09T21:48:53Z | Print a value to a writer as it would be written in Zig syntax as a (x) literal. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/nektro/zig-fmt-valueliteral/tags | MIT | [
"zig",
"zig-package"
]
| 12 | false | 2025-05-21T20:33:24Z | true | false | unknown | github | []
| zig-fmt-valueliteral
<a></a>
<a></a>
<a></a>
<a></a>
Print a value to a writer as it would be written in Zig syntax as a (x) literal.
Api
<ul>
<li><code>pub fn fmtValueLiteral(w: std.io.Writer, value: anytype, comptime print_type_name: bool) !void</code><ul>
<li><code>w</code> is an <code>anytype</code> for any value that implements <code>std.io.Writer</code>. It will then print the respective syntax literal to it.</li>
<li><code>value</code> is anything you'd like it to print. Should it fail to print a value you feel it should be able to please open an issue.</li>
<li><code>print_type_name</code> is a bool for whether or not you'd like it to print <code>@typeName(T)</code> or <code>.</code> when printing structs, enums, and unions.</li>
</ul>
</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/11513568?v=4 | mixtool | Hadron67/mixtool | 2021-08-19T07:47:54Z | CNC MIX file tool written in Zig | master | 0 | 1 | 1 | 1 | https://api.github.com/repos/Hadron67/mixtool/tags | - | [
"cnc",
"zig"
]
| 7 | false | 2021-10-10T05:00:10Z | true | false | unknown | github | []
| mixtool
A simple command-line tool used to view/modify .mix files in games like CNC, RA2, and their mods, especially Mental Omega.
Very much a work in progress, as file ID decoding and encryption are not implemented. | []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | zig-blake2x | x13a/zig-blake2x | 2021-12-02T18:36:40Z | BLAKE2X implememtation in zig. | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/x13a/zig-blake2x/tags | MIT | [
"blake2",
"crypto",
"zig",
"zig-lang"
]
| 82 | false | 2023-01-27T23:56:46Z | true | false | unknown | github | []
| zig-blake2x
<a>BLAKE2X</a> implememtation in zig.
Reference
<a>golang/crypto</a> | []
|
https://avatars.githubusercontent.com/u/46191274?v=4 | ZigSDL2Demo | Androthi/ZigSDL2Demo | 2021-07-20T09:13:14Z | A small demo to open an SDL window using Zig | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/Androthi/ZigSDL2Demo/tags | - | [
"sdl2",
"zig"
]
| 6 | false | 2025-02-16T00:12:01Z | true | false | unknown | github | []
| Zig SDL2 Demo
This demo is made possible by following an article written by Fabio Arnold
https://dev.to/fabioarnold/setup-zig-for-gamedev-2bmf
It is designed to be built on Windows OS, but a simple edit of the Build.zig file should make it possible to build on Linux.
Building
Built using zig version 0.9.0-dev.463+3e8394776
https://ziglang.org/download/
If you don't already have SDL2, download and install it whereever you keep your SDK files.
https://libsdl.org/release/SDL2-devel-2.0.14-VC.zip
To get this working on your Windows system, edit the Build.zig file
and set the sdl_path to where you installed your sdl2 libraries. | []
|
https://avatars.githubusercontent.com/u/2389051?v=4 | zig-unidecode | squeek502/zig-unidecode | 2022-01-02T09:25:55Z | Very approximate UTF-8 to ASCII transliterator (a Zig implementation of the Text::Unidecode Perl module) | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/squeek502/zig-unidecode/tags | 0BSD | [
"transliteration",
"unidecode",
"zig",
"zig-package",
"ziglang"
]
| 83 | false | 2024-05-11T15:21:34Z | true | false | unknown | github | []
| zig-unidecode
A <a>Zig</a> implementation of the <a>Text::Unidecode Perl module</a> to convert UTF-8 text into a (very) approximate ASCII-only transliteration. That is, this is "meant to be a transliterator of last resort."
For a more detailed description including motivation, caveats, etc, see:
https://metacpan.org/pod/Text::Unidecode
Examples
| UTF-8 | Transliterated ASCII |
| ------------- | ------------- |
| <code>"ÿéáh"</code> | <code>"yeah"</code> |
| <code>"北亰"</code> | <code>"Bei Jing "</code> |
| <code>"Славься"</code> | <code>"Slav'sia"</code> |
| <code>"[██ ] 50%"</code> | <code>"[## ] 50%"</code> |
Some things worth noting
<ul>
<li>The returned output will only contain ASCII characters (<code>0x00</code>-<code>0x7F</code>).</li>
<li>Any ASCII characters in the input will be unconverted in the output.</li>
<li>UTF-8 codepoints may be transliterated to a variable number of ASCII
characters (including 0).</li>
<li>UTF-8 codepoints > <code>0x7F</code> will never be transliterated to include any
ASCII control characters except <code>\n</code>.</li>
<li>Unknown UTF-8 codepoints may be transliterated to <code>[?]</code>.</li>
</ul>
The different functions provided
<code>unidecodeAlloc</code>
Takes an allocator in order to handle any input size safely. This should be used for most use-cases.
<code>unidecodeBuf</code>
Takes a <code>dest</code> slice that must be large enough to handle the transliterated ASCII. Because the output size can vary greatly depending on the input, this is unsafe unless it can be known ahead-of-time that the transliterated output will fit (i.e. comptime).
<code>unidecodeStringLiteral</code>
A way to transliterate a UTF-8 string literal into ASCII at compile time. | []
|
https://avatars.githubusercontent.com/u/6039952?v=4 | image.zig | gernest/image.zig | 2021-04-10T12:52:24Z | Image library for zig | master | 0 | 1 | 1 | 1 | https://api.github.com/repos/gernest/image.zig/tags | - | [
"image",
"jpeg",
"png",
"zig"
]
| 307 | false | 2021-11-15T03:00:02Z | true | false | unknown | github | []
| zig-image
Port of go <code>image</code> package to zig | []
|
https://avatars.githubusercontent.com/u/9265556?v=4 | vulkan-experiment | tonis2/vulkan-experiment | 2021-07-14T06:52:38Z | Zig + Vulkan with native C api | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/tonis2/vulkan-experiment/tags | - | [
"glfw",
"vulkan",
"zig"
]
| 1,436 | false | 2021-10-14T14:36:14Z | true | false | unknown | github | []
| Vulkan and zig examples
This <code>zig</code> + <code>vulkan</code> example, runs straight from Vulkan C api
Tested on Linux and with zig version <code>0.9.0 dev</code>
Requires external dependencies <code>vulkan</code> and <code>glfw</code> and zig library <code>zalgebra</code>
Clone this repo using <code>--recursive</code> to download zig dependencies.
To run example use <code>zig build basic</code> | []
|
https://avatars.githubusercontent.com/u/74844070?v=4 | autopkg | kacheproject/autopkg | 2021-09-12T01:15:51Z | Zig/C/C++ dependency management made easy. Autopkg is a library works with Zig Build System to simplify package management. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/kacheproject/autopkg/tags | - | [
"build",
"c",
"cpp",
"dependency-manager",
"package",
"zig"
]
| 29 | false | 2023-08-24T19:12:24Z | false | false | unknown | github | []
| Autopkg
Autopkg is a library works with zig build system to simplify package management.
Featured:
- Declarative experience
- Programable package
- Nested directory structure support
- Working with C headers and sources
Zig build system lack of these important QoL features. This library is intented to provide them.
| Zig Branch | Zig Version | Supported |
|------------|----------------|-----------|
| stable | 0.8.0, 0.8.1 | YES |
| master | 0.9.0+dev.1561 | YES |
Basic Usage
This library is zero-dependency. Just copy the <code>autopkg.zig</code> or refer by git submodule.
In the <code>build.zig</code> of the package <code>./package</code> you need to work with:
````zig
const autopkg = @import("autopkg/autopkg.zig");
/// <code>name</code> is the name you name.
/// <code>path</code> is relative path to this library directory.
pub fn package(name: []const u8, path: []const u8) autopkg.AutoPkgI {
return autopkg.genExport(.{
.name = name,
.path = path,
.rootSrc = "src/main.zig", // Use empty string if you don't have zig source file.
// You can specify more options about libraries and C sources, see source code autopkg.zig (don't worry, the code is short). All options works locally.
});
}
````
In the <code>build.zig</code> in your main package <code>.</code>:
````zig
const std = @import("std");
const autopkg = @import("autopkg/autopkg.zig");
pub fn package(name: []const u8, path: []const u8) autopkg.AutoPkgI {
const thePackageYouNeed = @import("./package/build.zig");
return autopkg.genExport(.{
.name = name,
.path = path,
.rootSrc = "src/main.zig",
.dependencies = &.{
autopkg.accept(thePackageYouNeed.package("package", "./package")),
},
});
}
pub fn build(b: *std.build.Builder) void {
const mode = b.standardReleaseOptions();
<code>var mainPackage = autopkg.accept(package("main", "."));
defer mainPackage.deinit();
var resolvedPackage = mainPackage.resolve(".", b.allocator) catch unreachable;
const lib = resolvedPackage.addBuild(b);
lib.setBuildMode(mode);
lib.install();
</code>
}
````
The <code>package()</code> function is not limited to the two parameters specified here. You can return alternative version of <code>AutoPkgI</code> depends on the arguments or even the environment.
If you don't want to specify an auto package and just want to depend on one using that, you could use <code>AutoPkg.dependedBy()</code>:
````zig
const thePackageYouWorkWith = @import("./package/build.zig");
const autopkg = @import("autopkg/autopkg.zig");
pub fn build(b: *std.build.Builder) void {
const mode = b.standardReleaseOptions();
<code>const resolvedThePackage = autopkg.accept(thePackageYouWorkWith.package("package", "./package")).resolve(".", b.allocator) catch unreachable; // You need to resolve the package first
const lib = b.addStaticLibrary("mypackage", "src/main.zig");
resolvedThePackage.dependedBy(lib);
lib.setBuildMode(mode);
lib.install();
</code>
}
````
Inside Memory Management
Autopkg will do multiple copy in heap to make sure the infomation alive:
<ul>
<li><code>genExport</code></li>
<li><code>AutoPkg.resolve</code></li>
</ul>
and <code>AutoPkg.deinit</code> will call <code>AutoPkg.deinit</code> of every <code>AutoPkg</code> it refered.
As the fact of <code>std.build.Builder.allocator</code> is an ArenaAllocator, you don't need to deinitilise the structure if you use with that (Just like above exmaple).
Internally autopkg uses a <code>std.heap.GeneralPurposeAllocator</code> to allocate memory when calling <code>genExport()</code>.
Remember: unrefered packages will cause memory leak!
Tests
Autopkg can automatically handle tests dependencies for you, and you can test the packages you work with if they set <code>doNotTest</code> to false (which is the default). Any package's tests will be skipped if it's <code>doNotTest</code> is <code>true</code>.
For older versions' autopkg, <code>doNotTest</code> is <code>true</code> by default.
If you will publish the package, it's recommended to set <code>doNotTest</code> as <code>true</code>.
````zig
const std = @import("std");
const autopkg = @import("autopkg/autopkg.zig");
pub fn package(name: []const u8, path: []const u8) autopkg.AutoPkgI {
const thePackageYouNeed = @import("./package/build.zig");
return autopkg.genExport(.{
.name = name,
.path = path,
.rootSrc = "src/main.zig",
.dependencies = &.{
autopkg.accept(thePackageYouNeed.package("package", "./package")),
},
.doNotTest = false, // though it's by default.
});
}
pub fn build(b: *std.build.Builder) void {
const mode = b.standardReleaseOptions();
const target = b.standardTargetOptions(.{});
<code>var mainPackage = autopkg.accept(package("main", "."));
defer mainPackage.deinit();
var resolvedPackage = mainPackage.resolve(".", b.allocator) catch unreachable;
const lib = resolvedPackage.addBuild(b);
lib.setBuildMode(mode);
lib.install();
var testStep = b.addStep("test" , "Run all tests");
testStep.dependOn(resolvedPackage.addTest(b, mode, target));
</code>
}
````
Addtional Testing
Zig build system's testing may not cover some files you want. To test these files, add them into <code>testSrcs</code>.
<code>Zig
pub fn package(name: []const u8, path: []const u8) autopkg.AutoPkgI {
const thePackageYouNeed = @import("./package/build.zig");
return autopkg.genExport(.{
.name = name,
.path = path,
.rootSrc = "src/main.zig",
.dependencies = &.{
autopkg.accept(thePackageYouNeed.package("package", "./package")),
},
.doNotTest = false, // though it's by default.
.testSrcs = &.{
"src/file1.zig",
"src/file2.zig",
},
});
}</code>
These addtional testings follow the <code>doNotTest</code> option as well.
C Source and Header Files
Autopkg can help you mixing zig and C sources with ease.
<code>zig
pub fn package(name: []const u8, path: []const u8) autopkg.AutoPkgI {
const thePackageYouNeed = @import("./package/build.zig");
return autopkg.genExport(.{
.name = name,
.path = path,
.rootSrc = "src/main.zig",
.includeDirs = &.{"include"},
.cSrcFiles = &.{"./src/main.c"},
.dependencies = &.{
autopkg.accept(thePackageYouNeed.package("package", "./package")),
},
.ccflags = &.{"-Wall", "-std=c11", "-g"},
});
}</code>
Autopkg will set up the build system to mix your zig files and C sources <code>cSrcFiles</code> (with <code>includeDirs</code> as include directories). C sources will be compiled with <code>ccflags</code>.
<code>includeDirs</code> will be added to the packages which depends on this package. It's recommended that only put the files will be directly refered in your zig package and choose name carefully.
Contributing
Suggestion/Pull Request welcome!
Maintainer
<code>Rubicon Rowe <l1589002388 & gmail.com></code>
License
<code>Apache-2.0</code>. | []
|
https://avatars.githubusercontent.com/u/52403031?v=4 | hd-mp3 | cs-t1/hd-mp3 | 2021-08-03T14:02:37Z | HID driver for the Hercules DJ Control MP3 controller with support for advanced LED blinking and button on-update methods | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/cs-t1/hd-mp3/tags | GPL-3.0 | [
"dj-controller",
"driver",
"hercules",
"zig"
]
| 86 | false | 2022-01-17T02:43:41Z | true | false | unknown | github | []
| hd-mp3
Custom userspace HID driver for the Hercules DJ Control MP3.
Data input
A small and naive daemon receives the packets from the USB interface and decodes it. It is provided the possibility of assigning custom functions to be executed on value change, and this on a per button/slider basis.
For now, these functions do not get launched in a separate thread, but this is the long-term goal.
Data output
A simple LED-controlling daemon drives the LEDs. It runs in a different thread and can receive requests via a mailbox. It is capable of handling asynchronously blinking LEDs efficiently through a time-based priority queue. | []
|
https://avatars.githubusercontent.com/u/56988989?v=4 | zrs | Potato-Industries/zrs | 2021-12-10T23:18:42Z | portable ziglang based reverse shell | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/Potato-Industries/zrs/tags | - | [
"reverse-shell",
"zig",
"ziglang"
]
| 20 | false | 2022-09-17T07:39:20Z | true | false | unknown | github | []
| zrs
portable Ziglang based reverse shell
https://ziglang.org/
<strong>Required package:</strong>
'network.zig'
https://github.com/MasterQ32/zig-network
```
root@84f9b9ce9b42:/var/tmp/zig-linux-aarch64-0.9.0-dev.1936+77836e08a# ls src/main.zig
src/main.zig
root@84f9b9ce9b42:/var/tmp/zig-linux-aarch64-0.9.0-dev.1936+77836e08a# ./zig build
root@84f9b9ce9b42:/var/tmp/zig-linux-aarch64-0.9.0-dev.1936+77836e08a# file zig-out/bin/zig-linux-aarch64-0.9.0-dev.1936+77836e08a
zig-out/bin/zig-linux-aarch64-0.9.0-dev.1936+77836e08a: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, with debug_info, not stripped
```
<strong>Cross Compile</strong>
https://ziglang.org/learn/overview/#cross-compiling-is-a-first-class-use-case
Enjoy~ | []
|
https://avatars.githubusercontent.com/u/2859122?v=4 | texture-packer | kooparse/texture-packer | 2021-12-27T14:12:02Z | A dynamic texture packer using a naive packer algorithm. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/kooparse/texture-packer/tags | - | [
"gamedev",
"zig"
]
| 3 | false | 2021-12-27T21:29:25Z | true | false | unknown | github | []
| Texture Packer
Pack given bitmaps into a single one.
Note: This library uses a naive rectangle packing algorithm. It's absolutely
not the most efficient one, but implementation complexity is very low.
Example:
```
const Packer = TexturePacker(u8, 20, 50);
var packer = Packer{};
const rect = std.mem.zeroes([10 * 10]u8);
const a = try packer.pushBitmap(10, 10, &rect);
try expectEqual(a.x, 0);
try expectEqual(a.y, 0);
const b = try packer.pushBitmap(10, 10, &rect);
try expectEqual(b.x, 10);
try expectEqual(b.y, 0);
const c = try packer.pushBitmap(10, 10, &rect);
try expectEqual(c.x, 0);
try expectEqual(c.y, 10);
// All packed bitmaps are stored there.
const result = packer.bitmap;
```
A good resource about packing algorithms:
<a>Exploring rectangle packing algorithms by David Colson</a> | []
|
https://avatars.githubusercontent.com/u/3598852?v=4 | niceware-cli | svercl/niceware-cli | 2021-10-09T23:10:53Z | A command line tool for generating secure and memorable passwords. | main | 2 | 1 | 0 | 1 | https://api.github.com/repos/svercl/niceware-cli/tags | MIT | [
"cli",
"niceware",
"zig"
]
| 272 | false | 2024-05-13T01:06:38Z | true | false | unknown | github | []
| niceware
A command line tool for generating secure and memorable passwords.
This is a Zig port of <a>niceware</a> with a CLI interface.
See original project README for more information.
Requirements
<ul>
<li>Zig 0.12.0</li>
</ul>
Building
<code>zig build -Doptimize=ReleaseSafe</code>
Running the tests
<code>zig build test</code>
How to use
To get an overview of all commands you can run <code>niceware --help</code>.
from-bytes
Converts from bytes (a hex string) into a passphrase.
<code>niceware from-bytes e4c320324baf3a03</code> results in <code>torpedoed chef fain disabling</code>
generate
Generates a random passphrase. You may specify an optional size when calling this command.
to-bytes
Converts the passphrase into its bytes representation.
<code>niceware to-bytes stroganoff inharmonic allergic tangy</code> results in <code>d7976e08033bde4a</code>
Credits
This wouldn't be possible without the <a>original</a>.
Huge shoutout to healeycodes for the <a>Rust port</a>.
The core library used here is a direct port of it. | []
|
https://avatars.githubusercontent.com/u/52403031?v=4 | arlustre | cs-t1/arlustre | 2021-11-08T22:26:50Z | Arduino interface for the Heptagon synchronous dataflow-oriented language written in Zig. | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/cs-t1/arlustre/tags | AGPL-3.0 | [
"arduino-library",
"arduino-uno",
"dataflow-programming",
"heptagon",
"synchronous-programming",
"zig"
]
| 143 | false | 2023-11-01T17:11:00Z | false | false | unknown | github | []
| (WIP)
Arlustre
Arduino interface for the <a>Heptagon</a> synchronous language written in <a>Zig</a>. It should provide a kinda-low-level interface to any heptagon program, through the custom Heptagon Zig backend. The whole low-level Arduino core-library is implemented using Zig. ⚠️ Only works for the standard Arduino Uno board.
Non-exhaustive list of functionning features:
<ul>
<li>Very simple Zig backend, not extensively tested (all operations on arrays are not supported for now)</li>
<li>Zig Arduino Libcore with custom bootstraping stack, interrupts, Serial, GPIO</li>
<li>Interface to Heptagon for both GPIO allocation/read/write operatiosn as well as printing (more to come)</li>
</ul>
Achievements
Things I have achieved so far :
<ul>
<li>Arduino libcore covering a not-to-bad proportion of the features available on the Arduino Uno platform (GPIO, Serial, some basic timer interrupts so far)</li>
<li>Automated build using <code>zig build</code></li>
<li>Small Lustre interface containing GPIO-{declaration, read, write}.</li>
<li>Lustre test program showing a proof-of-concept with LEDs, timers, a potentiometer and a button.</li>
</ul>
How to use
Programming
The program's main logic is located in the <code>src/top.lus</code> Lustre file. The interface is defined in <code>src/interface.epi</code>. Both files should not be moved or renamed, as the build system is quite rudimentary and assumes the existence of these files at these locations.
<code>src/lib</code> contains the Arduino libcore in pure Zig. It contains all basic fonctionnalities regarding MMIO, GPIO, interrupts, timers and the Serial interface. The <code>src/libz/interrupt.zig</code> file contains bindings to <code>src/main.zig</code> for the moment but this should be removed and replaced by a runtime ISR declaration during the booting process, thus making the <code>Libz</code> intrinsically independant from the application.
<code>build.zig</code> is the building script.
<code>boot.zig</code> is the entry point of the program. It handles both the clearing of ths <code>.bss</code> segment and the data-loading from Flash to RAM.
<code>start.zig</code> defines the main function : <code>bootstrap</code> where all interrupts and timers should be initialized. This function is called by <code>_start</code> after the booting proccess and, in this particular application, resets the state of the Lustre program.
<code>main.zig</code> is automatically generated but modified a bit by hand (TODO make this fully automatic) and defines global <code>reset</code> and <code>step</code> functions to drive the entire transpilled Lustre program.
<code>top.zig</code> is automatically generated by <code>heptc</code> from <code>top.lus</code>. It contains all the Lustre logic, i.e. the "heart of the program", everything else being only the booting process and auxiliary functions.
Prerequisites
<ul>
<li><code>ocaml</code> and some other <code>opam</code> libraries to compile my custom fork of <code>heptagon</code> (available as a submodule).</li>
<li><code>zig</code> version >= <code>0.8</code> (source available <a>on Github</a> or via some shady repackers s.a. <code>snap</code> or <code>flatpak</code> or through the AUR). Do note that Zig is still in pre-1.0 version so it tends to be not so stable now and then. If a strange behaviour is encountered, do try another (maybe more recent or more stable) release.</li>
<li><code>screen</code></li>
<li><code>avrdude</code></li>
<li><code>avr-gcc</code> for the linking process</li>
<li>(optional) <code>avr-objdump</code> needed to use <code>zig build objdump</code></li>
</ul>
How to compile
<ul>
<li><code>make</code> root directory. This should compile the modified version of <code>heptc</code>, run it on the test Lustre program and build the generated Zig code.</li>
<li>in the <code>src</code> subdirectory : </li>
<li><code>zig heptc</code> : runs <code>heptc</code> on <code>interface.epi</code> and <code>top.lus</code> and moves the generated <code>top.zig</code> in <code>./src</code></li>
<li><code>zig build</code> : Both transpiles the Lustre program and builds the resulting Zig program into an Arduino-compatible binary</li>
<li><code>zig build upload</code> : does everything mentionned before (<code>heptc</code>, compiles the Zig program) and uploads the program to the Arduino using a generic port using <code>avrdude</code> (TODO add port as an optional argument)</li>
<li><code>zig screen</code> : does everything above + opens a <code>screen</code> session with the arduino on the same port (TODO add port as an optional argument)</li>
</ul>
Acknowledgments
Thanks to <a>FireFox317</a> for their <a>Arduino Zig basis</a>.
Thanks to <a>Silversquirl</a> for their help with linker issues. | []
|
https://avatars.githubusercontent.com/u/1892046?v=4 | zga | nsmryan/zga | 2021-05-13T23:58:55Z | A Genetic Algorithm and Robust Gene Expression Programming implementation in Zig | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/nsmryan/zga/tags | - | [
"ga",
"rgep",
"zig"
]
| 16 | false | 2025-05-20T21:59:22Z | false | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/16592366?v=4 | ziggerish | bivoje/ziggerish | 2022-01-19T03:58:05Z | Brainfuck compiler with minimum compile dependency, written in zig. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/bivoje/ziggerish/tags | - | [
"brainfuck",
"brainfuck-compiler",
"compiler",
"compilers",
"programming-language",
"zig",
"ziglang"
]
| 67 | false | 2023-01-19T21:22:37Z | true | false | unknown | github | []
| Ziggerish
Brainfuck compiler written in Zig.
Build
This project is tested with <a><code>zig-linux-x86_64-0.10.0-dev.479+5e60ee412</code></a>.
Compatibility with other versions of zig is not known.
Download and install zig compiler then
<code>zig build</code>
will create the executable in <code>zig-out/bin/ziggerish</code>.
Example
Hello world
Simple hello world program copied from wikipedia page
<code>zig build run -- samples/hello.bf : ?target=linux_x86_64 ?alloc=7 : ll : main</code>
Life
life automaton simulator written by Linus Akesson
found at <a>here</a>.
<code>ziggerish samples/hello.bf : ?target=linux_x86_64 ?alloc=-1000 : as : hello</code>
DBFI
shorted brainfuck interpreter written in brainfuck
found at <a>here</a>.
<code>ziggerish samples/dbfi.bf : ?target=linux_x86 : gcc +inlined -libc : dbfi
(cat samples/hello.bf; echo -n '!') | ./dbfi</code>
Usage
<code>ziggerish <source> : <general_options> : <method> <method_options> : <dest></code>
<code>ziggerish</code> gets compile options from commandline arguments in unconventional, structured way.
4 fields being colon (<code>:</code>) separated are required where each can be left omitted for default value.
Note that you can't omit space between colons and give <code>ziggerish a.bf ::: a.out</code>,
as parameters are tokenized by whitespaces in current implimentation.
source and dest
Simply specify source path and destination path.
In current implementation, when multiple paths are given, only the last one is recognized.
general options
Unlike other unix programs, options have the form <code>?<key>=<value></code>.
If the value is boolean you can use syntactic sugar <code>+<key></code> for <code>true</code> or <code>-<key></code> for <code>false</code>.
The possible options are:
- verbose: = false, true
boolean sitch for verbose output while compilation
- warning: = true, false
boolean switch for print warning while compilation
- alloc: 1000, isize
how to allocate cells buffer in memory.
+ positive integer: static allocation of given size, buffer range checked
+ negative integer: static allocation of given size, buffer range unchecked
+ 0: dynamic allocation, buffer grows as needed. no supported for llvm, gcc with nolibc
- eof_by: noop, neg1, zero
what <code>,</code> instruction do when EOF encountered. there are no consensus for behavior on EOF,
so each bf code assumes one of the options listed above.
selecting the wrong option may result in unexpected behavior of compiled program.
+ noop: does nothing leaves the cell unchanged
+ neg1: sets the cell value to 255 (-1)
+ zero: sets the cell value to 0
- target: linux_x86_64, linux_x86
march of target object file.
method and method options
<code><method></code> selects which backends to use while compiling.
<code><method_options></code> has same format as <code><general_options></code> while supported keys are method specific.
Currently suppoted methods are
- gcc
generate C code and use <code>gcc</code> to produce an executable.
+ inlined: false, true
boolean flag to inline routines for brainfuck instructions.
currently, only <code>.</code> and <code>,</code> are effected, and <code>></code> and <code><</code> are inlined regardlessly.
+ libc: true, false
boolean flag to use standard libc. without it, the compiler uses syscall directly.
with this flag on, the code cannot be inlined, in current implementation
+ temp_path: temp.c, string
temporary path for geneated c code
- as
generate AT&T assembly code and uses <code>as</code> and <code>ld</code> to produce an executable.
+ temp_path_s: temp.s, string
temporary path for assembly code
+ temp_path_o: temp.o, string
temporary path for object file that is generated by <code>as</code>
- ll
generate llvm code and use <code>clang</code> to produce an execuable.
+ temp_path_ll: temp.ll, string
temporary path for llvm code
other links
<ul>
<li><a>bfc</a>: utterly over-engineered brainfuck compiler written in Rust.</li>
</ul>
TODO
[ ] impliment streamed input/output
[ ] --help option?
[ ] better, detailed error message.
use enum-either rather than error set
[ ] support intel assembly syntax?
[ ] organize tests
[ ] add tests
[ ] optimizaion
use ir (add 4 etc..) <- need to ge/le rather than ne for boundary check
[ ] remove unnecessary -q instr, it inflates machine code size
[ ] boundary check when accessing the value rather than moving the pointer
[ ] writer monad, funcionize code snippet generation
parameterize registers in compile_as
[ ] what if compilation takes too long? < like kernel compile?
memory management use other than arena
[ ] windows binary support
[ ] resolve TODOs and FIXMEs
[ ] impliment inotifywait in build.zig
<code>inotifywait src</code> is too noisy, as vim never just writes to the file
vim creates and writes to filename~ file stead of the file itself
and then deletes original and moves the file
with auto saves and temp files, this behavior makes watch-test run multiple times
[ ] enable compiling with debugging infos
[ ] verbos compiling (dump option only if)
[ ] compile pipeline design
[ ] option for how to handle temp files?
[ ] immediate executable generation
[ ] inline asm. it inflates exe size but may have better performance as there's less jumps.
[ ] alloc=dynamic in c-nostdlib/llvm using alloca(). | []
|
https://avatars.githubusercontent.com/u/2910679?v=4 | zig-ron | teh-cmc/zig-ron | 2021-10-28T16:54:55Z | [WIP] A robust, efficient implementation of the Rusty Object Notation (RON) for the Zig programming language. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/teh-cmc/zig-ron/tags | MIT | [
"parser",
"ron",
"zig"
]
| 26 | false | 2023-10-27T21:07:08Z | true | false | unknown | github | []
| Zig-RON
<em><strong>wip</strong></em>
Hopefully: a robust, efficient implementation of the <a>Rusty Object Notation</a> for the Zig programming language.
This is a work in progress: you can and should expect missing docs, miscellaneous bugs, a general lack of polish, etc.
The deserializer should already be in a pretty usable state though, hence this early release.
There simply isn't a serializer yet, that's the easy part though :)
Feel free to reach out either via the issue tracker or on Zig discord (<code>clem#0498</code>).
Usage
```zig
const std = @import("std");
const ron = @import("ron");
const MyStruct = struct {
bool: bool,
float: f32,
int: i42,
string: []const u8,
char: ron.Char,
unit: ron.Unit,
<code>array_list: std.ArrayList(u32),
slice: []u32,
string_map: std.StringArrayHashMap([]const u8),
map: std.AutoArrayHashMap(bool, []const u8),
option: ?[]const u8,
enums: enum { a, b, c },
unions: union(enum) { a: bool, b: []const u8, c: f32 },
any: ron.Value, // Generic heterogeneous values
nested: ?*@This(),
default: []const u8 = "some default value",
</code>
};
const data =
\MyStruct(
\ bool: true,
\ float: 42.420,
\ int: 666,
\ string: "ガタカへようこそ",
\ char: '🚁',
\ unit: (),
\
\ array_list: [1, 2, 3, 4],
\ slice: [5, 6, 7, 8],
\
\ string_map: { "hello": "world" },
\ map: { false: "is false", true: "is not false" },
\
\ option: Some("\u{263A}"),
\ enums: b,
\ unions: c(666.111),
\ any: seq([string("hey"), bool(true), float(42.42)]),
\
// Tuple to struct coercion!
\ nested: Some((
\ false, 1.0, 2, "xxx", 'X', (),
\ [], [], {}, {},
\ None, a, b("nope!"), option(None),
\ None,
\ )),
\
// This will be silently ignored.
\ field_that_doesnt_exist: DoesntExist(
\ xxx: 42,
\ 42: "xxx"
\ ),
\)
;
pub fn main() !void {
var allocator = std.heap.page_allocator;
<code>var deser = ron.Deserializer.init(allocator);
// clears internal parser resources
defer deser.deinit();
// clears data allocated for the end-user (arrays, maps, escaped strings...)
defer deser.parseFree();
var tokens = &ron.Lexer.init(data).token_stream;
const res = deser.parse(MyStruct, tokens) catch |err| {
try deser.report(std.io.getStdErr().writer());
return err;
};
_ = ron.debug_ext.dbg(res);
</code>
}
```
License
<a>MIT</a> | []
|
https://avatars.githubusercontent.com/u/177491?v=4 | docker-zig | trashhalo/docker-zig | 2021-12-23T22:50:38Z | docker image with zig and gyro for aarch64 | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/trashhalo/docker-zig/tags | - | [
"docker",
"zig"
]
| 2 | false | 2022-02-20T22:10:31Z | false | false | unknown | github | []
| Docker Zig
Docker file with zig 0.9 and gyro 0.4.0. aarch64 architecture. Created to work around gyro not having a working build for m1 mac os x. https://github.com/mattnite/gyro/issues/148
Usage
```
cd into cloned docker-zig
docker build -t zig:latest .
cd into your gyro based zig project
docker run --mount type=bind,source="$(pwd)",target=/app zig:latest gyro build test
``` | []
|
https://avatars.githubusercontent.com/u/2100771?v=4 | zig-r-example | matthewwiese/zig-r-example | 2021-10-03T16:12:37Z | Example package that illustrates calling Zig from R. | main | 0 | 1 | 2 | 1 | https://api.github.com/repos/matthewwiese/zig-r-example/tags | ISC | [
"r",
"r-package",
"rstats",
"zig",
"ziglang"
]
| 5 | false | 2024-06-28T07:04:27Z | false | false | unknown | github | []
| Example R Package using Zig
This repository is an experiment in using <a>Zig</a> as an alternative to C (or <a>C++</a>) in R packages.
Installation
<code>R
library(devtools)
install_github("matthewwiese/zig-r-example")</code>
<strong>NOTE</strong>
If you encounter <code>/bin/bash: zig: command not found</code> when using the installation method above, please read this section.
Unlike R invoked from the terminal, RStudio does not get its PATH information from your shell, but from system-wide settings. Prepend to RStudio's PATH the directory containing your <code>zig</code> executable; use the following command as guidance:
<code>R
Sys.setenv(PATH=paste("/path/to/zig:", Sys.getenv("PATH"), sep=""))</code>
For more information, see <a>this StackOverflow</a> answer.
Development
Requirements
The Zig code in this package has been tested using release <a>0.8.1</a>. Make sure you have downloaded Zig and it is available as <code>zig</code>.
I've only tested this on Linux (Ubuntu 20.04) so far; please see the <a>Building</a> section for more information.
Local Install
To package and install locally, run the following commands in your terminal. You must be in the parent directory of wherever you cloned this repo.
<code>bash
R CMD build zig-r-example
R CMD INSTALL zigrexample_0.1.tar.gz</code>
Building
This is where things get... hacky. The "magic" is contained within <a><code>src/Makevars</code></a>, which we are using in a <em>very</em> nonstandard way. Eventually, I hope to use <code>zig cc</code> and <code>zig c++</code> so that heterogenous code is supported without (ideally) any deviation from the normal R package build process.
Since this is still experimental, I'm focusing on refining the ergonomics for my own development environment. Therefore, this package won't work on Windows or macOS yet. However, I see no reason why it <em>shouldn't</em> work on Windows or macOS; submit an issue and we can work on it together! | []
|
https://avatars.githubusercontent.com/u/53379023?v=4 | zig-ipcrypt | x13a/zig-ipcrypt | 2021-12-06T21:44:03Z | ipcrypt implementation in zig. | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/x13a/zig-ipcrypt/tags | MIT | [
"zig",
"zig-lang"
]
| 5 | false | 2023-01-27T23:56:46Z | true | false | unknown | github | []
| zig-ipcrypt
<a>ipcrypt</a> implememtation in zig.
Reference
<a>silkeh/ipcipher</a> | []
|
https://avatars.githubusercontent.com/u/65508234?v=4 | programming-junky | Ulrich-Tonmoy/programming-junky | 2022-01-21T07:31:02Z | 👨💻 A repository that host all the projects build while learning the tools/language. | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/Ulrich-Tonmoy/programming-junky/tags | - | [
"python",
"zig"
]
| 47,366 | false | 2025-01-17T10:41:23Z | false | false | unknown | github | []
| programming-junky
A repository that host all the projects build while learning the tools/language.
<ul>
<li><a>C++ project setup with zig c++ compiler</a></li>
<li><a>Raylib C++ project setup with zig c++ compiler</a></li>
<li><a>Raylib C++ Pong with zig c++ compiler</a></li>
<li><a>Raylib Zig project setup</a></li>
</ul> | []
|
https://avatars.githubusercontent.com/u/116107?v=4 | chip8z | ltriant/chip8z | 2021-10-01T06:20:47Z | CHIP-8 emulator | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/ltriant/chip8z/tags | NOASSERTION | [
"chip-8",
"chip-8-emulator",
"emudev",
"emulator",
"emulator-programming",
"emulators",
"gamedev",
"sdl",
"zig"
]
| 23 | false | 2023-02-02T20:42:14Z | true | false | unknown | github | []
|
<blockquote>
Kill the C version, and let the Zig version be born
</blockquote>
— Aemon Targaryen (probably)
chip8z
A CHIP-8 emulator, written in Zig, as a direct port from <a>my old C version</a>.
I'm also using this as a place to try out Zig-isms.
Building
<a>SDL2</a> is required for the graphics, and it can be installed via many different package managers:
<code>$ brew install sdl2
$ sudo apt-get install libsdl2-dev
$ sudo yum install SDL2-devel</code>
Or see the <a>libsdl installation documentation</a> for more options.
After that, it can be built with <a>the Zig toolchain</a>:
<code>$ zig build
...</code>
This currently builds with Zig 0.11, so it will not build with older versions.
Running
ROMs can be sourced from anywhere you like, however I recommend getting them from <a>dmatlack/chip8</a>. ROMs can be invoked with the path to the ROM as the argument:
<code>$ zig-out/bin/chip8z roms/pong.ch8</code>
Keyboard
The original CHIP-8 keypad is on the left, and what I've mapped it to on a QWERTY keyboard is on the right:
<code>Keypad Keyboard
+-+-+-+-+ +-+-+-+-+
|1|2|3|C| |1|2|3|4|
+-+-+-+-+ +-+-+-+-+
|4|5|6|D| |Q|W|E|R|
+-+-+-+-+ => +-+-+-+-+
|7|8|9|E| |A|S|D|F|
+-+-+-+-+ +-+-+-+-+
|A|0|B|F| |Z|X|C|V|
+-+-+-+-+ +-+-+-+-+</code>
Issues
There are various quirks, which probably won't be fixed. | []
|
https://avatars.githubusercontent.com/u/16408073?v=4 | minesolver | LewisGaul/minesolver | 2021-02-22T00:48:28Z | Minesweeper solver written in Zig and Python, supporting multiple mines per cell | main | 3 | 1 | 0 | 1 | https://api.github.com/repos/LewisGaul/minesolver/tags | - | [
"minesweeper",
"solver",
"zig"
]
| 819 | false | 2024-05-29T09:12:33Z | false | false | unknown | github | []
| <a></a>
Minesolver
A minesweeper solver.
Contents of the repository:
- <a>Design notes</a>
- <a>Zig implementation</a>
- <a>Rough Python implementation</a>
- <a>Examples in the form of Python tests</a> | []
|
https://avatars.githubusercontent.com/u/38368197?v=4 | Zasterizer | JuanDiegoMontoya/Zasterizer | 2021-07-29T08:18:46Z | A simple rasterizer written in Zig. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/JuanDiegoMontoya/Zasterizer/tags | - | [
"graphics-programming",
"rasterizer",
"zig"
]
| 103 | false | 2021-10-31T09:18:09Z | true | false | unknown | github | []
| Zasterizer
A Zig port of <a>this C rasterizer</a>.
Running
<ol>
<li><code>zig build run</code></li>
</ol>
Todo
<ul>
<li>Fix an apparent truncation error that results in jagged edges on some triangles</li>
</ul>
Gallery
| []
|
https://avatars.githubusercontent.com/u/79355443?v=4 | zmfr | chw-git/zmfr | 2021-02-20T10:07:06Z | minimal font rasterizer for zig | master | 3 | 1 | 0 | 1 | https://api.github.com/repos/chw-git/zmfr/tags | Unlicense | [
"freetype2",
"zig"
]
| 191 | false | 2022-12-05T01:20:57Z | false | false | unknown | github | []
| zmfr
minimal font rasterizer for zig
Has to be linked against freetype and c at the moment.
For building and running the example:
<code>zig build-exe example.zig -l freetype -l c
./example</code>
Or the same example in form of a test:
<code>zig test font.zig -l freetype -l c</code>
The example font is copied from https://github.com/bluescan/proggyfonts and licenced under MIT | []
|
https://avatars.githubusercontent.com/u/54189157?v=4 | zigvale-barebones | nailuj29/zigvale-barebones | 2021-11-17T21:35:24Z | A barebones kernel for zigvale | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/nailuj29/zigvale-barebones/tags | MIT | [
"limine",
"osdev",
"stivale2",
"zig",
"ziglang",
"zigvale"
]
| 1,181 | false | 2021-11-18T00:15:17Z | false | false | unknown | github | []
| zigvale-barebones
A barebones kernel using the <a>zigvale</a> library
Build instructions
You will need the following installed
- <a>gyro</a>
- <a>zig master</a>
- <a>qemu</a>
Install them however you want, as long as the <code>gyro</code>, <code>zig</code>, and <code>qemu-system-x86_64</code> executables are on your <code>PATH</code>, then simply run <code>make run</code> to run the OS | []
|
https://avatars.githubusercontent.com/u/12070598?v=4 | zlox | rvcas/zlox | 2021-08-23T03:25:37Z | Crafting Interpreters Part 3 | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/rvcas/zlox/tags | MIT | [
"compiler",
"garbage-collection",
"interpreter",
"virtual-machine",
"zig"
]
| 3 | false | 2023-01-26T00:38:23Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/40190339?v=4 | brainfuckz | daneelsan/brainfuckz | 2021-03-17T05:49:02Z | A Brainfuck interpreter written in Zig | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/daneelsan/brainfuckz/tags | MIT | [
"brainfuck",
"virtual-machine",
"zig"
]
| 226 | false | 2025-03-09T16:58:50Z | true | false | unknown | github | []
| brainfuckz
A Brainfuck interpreter written in <a>Zig</a>.
```bash
$ brainfuckz help
Usage: brain [command]
Commands:
code [BRAIN] Give brainfuck code to execute
file [PATH] Execute the code found in a .brain file
help Print this help message and exit
test Enters interactive mode
```
Example
<strong>code</strong>
Run a simple Brainfuck program that prints the letter 'H':
<code>bash
$ brainfuckz code '>+++++++++[<++++++++>-]<.'
H</code>
Print the classic "Hello world!":
```bash
$ brainfuckz code '>+++++++++[<++++++++>-]<.>+++++++[<++++>-]<+.+++++++..+++.[-]
<blockquote>
++++++++[<++++>-] <.>+++++++++++[<++++++++>-]<-.--------.+++
.------.--------.[-]>++++++++[<++++>- ]<+.[-]++++++++++.'
Hello world!
```
</blockquote>
<strong>file</strong>
Run one of the many Brainfuck programs stored in the <code>program/</code> subfolder:
<code>bash
$ brainfuckz file program/MorseTranslate.brain
Brainfuck
-... ..--.- ..--.- ..--.- ..--.- ..--.- ..--.- ..--.- ..--.- -...-</code>
A <a>Mandelbrot</a> program:
<code>bash
$ brainfuckz file program/Mandelbrot.brain</code>
<strong>test</strong>
Enter a simple Brainfuck REPL and test simple code:
<code>bash
$ brainfuckz test
brainfuckz> >+++++++++[<++++++++>-]<.
H
brainfuckz></code>
Build
```bash
Pull down this project
$ git clone https://github.com/daneelsan/brainfuckz.git
$ cd brainfuckz
Tested on
$ zig version
0.14.0
Build in ReleaseFast mode to speed up performance by >10x compared to the default debug mode
$ zig build -Doptimize=ReleaseFast
For convenience, copy the executable to the top-level directory
$ cp zig-out/bin/brainfuckz brainfuckz
```
Resources
<ul>
<li><a>Basics of BrainFuck</a></li>
<li>https://thorstenball.com/blog/2017/01/04/a-virtual-brainfuck-machine-in-go/</li>
<li>http://www.bf.doleczek.pl/</li>
<li>https://en.wikipedia.org/wiki/Brainfuck</li>
<li>https://github.com/daneelsan/BrainVirtualMachine</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/104643?v=4 | kilo | charlieman/kilo | 2022-01-16T20:58:56Z | https://viewsourcecode.org/snaptoken/kilo/ built in zig | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/charlieman/kilo/tags | - | [
"zig"
]
| 23 | false | 2025-04-27T18:52:26Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/43040593?v=4 | sndio-zig | dantecatalfamo/sndio-zig | 2022-01-28T22:10:16Z | sndio bindings for zig | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/dantecatalfamo/sndio-zig/tags | - | [
"bindings",
"freebsd",
"linux",
"openbsd",
"sndio",
"zig"
]
| 17 | false | 2022-02-23T00:30:54Z | true | false | unknown | github | []
| sndio-zig
<a>sndio</a> bindings for zig
Provides both native bindings and a zig wrapper
```zig
hdl = sio_open(...)
sio_write(hdl, arr, 5)
hdl.write(arr, 5)
```
Importing
```zig
const addSndio = @import("sndio-zig/build.zig").addSndio;
pub fn build(b: *std.build.Builder) void {
[...]
const exe = b.addExecutable("example", "src/main.zig");
addSndio(exe);
[...]
}
``` | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-bencode | nektro/zig-bencode | 2021-04-04T12:26:06Z | Bencode parser for Zig. | master | 0 | 1 | 1 | 1 | https://api.github.com/repos/nektro/zig-bencode/tags | MIT | [
"bencode",
"zig",
"zig-package"
]
| 54 | false | 2025-05-21T20:33:24Z | true | false | unknown | github | []
| zig-bencode
<a></a>
<a></a>
<a></a>
<a></a>
Bencode parser for Zig.
https://en.wikipedia.org/wiki/Bencode
https://www.bittorrent.org/beps/bep_0003.html#bencoding
Usage
Add the following to the bottom of your <code>zigmod.yml</code>
<code>yml
dependencies:
- src: git https://github.com/nektro/zig-bencode</code>
In your code
```zig
const bencode = @import("bencode");
pub fn main() !void {
var gpa = std.heap.GeneralPurposeAllocator(.{}){};
const alloc = &gpa.allocator;
<code>const file = @embedFile("./some/path/to.torrent");
var buf = std.io.fixedBufferStream(file);
const r = buf.reader();
const ben = try bencode.parse(r, alloc);
// do something with `ben`...
</code>
}
``` | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-detect-license | nektro/zig-detect-license | 2021-07-28T07:05:50Z | Given an input text guess which SPDX license it most likely is an instance of | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/nektro/zig-detect-license/tags | MIT | [
"zig",
"zig-package"
]
| 13 | false | 2025-05-21T20:33:44Z | true | false | unknown | github | []
| zig-detect-license
<a></a>
<a></a>
<a></a>
<a></a>
Given an input text guess which SPDX license it most likely is an instance of
Usage
<ul>
<li>
<code>pub fn detect(alloc: *std.mem.Allocator, license_src: []const u8) ![]const u8</code>
<ul>
<li>Given an input string, will return the SPDX license identifier for the closest guess to which one it might be</li>
</ul>
</li>
<li>
<code>pub fn detectInDir(alloc: *std.mem.Allocator, dir: std.fs.Dir) !?[]const u8</code>
<ul>
<li>Given a directory, will search for a <code>LICENSE</code> file and return the guess for which one it is. Will return <code>null</code> if the license file can not be found. If this returns null when you do indeed have a license file, please help expand the search examples by submitting a bug report.</li>
</ul>
</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/1625198?v=4 | raytracer-zig | Ryp/raytracer-zig | 2021-11-05T07:19:49Z | WIP Raytracer | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/Ryp/raytracer-zig/tags | MIT | [
"raytracer",
"zig"
]
| 12 | false | 2021-12-26T20:53:48Z | true | false | unknown | github | []
| Raytracer
Building
This should get you going after cloning the repo:
<code>sh
$ zig build run</code> | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | zig-unicode-uca | nektro/zig-unicode-uca | 2021-05-10T09:46:41Z | Zig bindings for the contributory data files for the Unicode Collation Algorithm. | master | 0 | 1 | 0 | 1 | https://api.github.com/repos/nektro/zig-unicode-uca/tags | MIT | [
"zig",
"zig-package"
]
| 1,358 | false | 2025-05-21T20:33:29Z | true | false | unknown | github | []
| zig-unicode-uca
<a></a>
<a></a>
<a></a>
<a></a>
Zig bindings for the Unicode Collation Algorithm
Last updated as of Unicode 16.0.0
https://www.unicode.org/reports/tr10/
<blockquote>
This report is the specification of the Unicode Collation Algorithm (UCA), which details how to compare two Unicode strings while remaining conformant to the requirements of the Unicode Standard. The UCA also supplies the Default Unicode Collation Element Table (DUCET) as the data specifying the default collation order for all Unicode characters.
</blockquote>
https://www.unicode.org/Public/UCA/latest/
Usage
This package provides <code>.allkeys</code> and <code>.decomps</code> namespaces.
License
Code here is MIT
Source data files are https://www.unicode.org/license.html | []
|
https://avatars.githubusercontent.com/u/96705314?v=4 | w4-lander | w4-lander/w4-lander | 2021-12-18T06:21:29Z | A lunar-lander type retro video game, written in Zig for the WASM-4 fantasy console. | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/w4-lander/w4-lander/tags | - | [
"fantasy-console",
"game",
"gamedev",
"lunar-lander",
"retrogaming",
"wasm",
"wasm4",
"zig"
]
| 519 | false | 2024-08-19T09:06:03Z | true | false | unknown | github | []
| w4-lander
A lunar-lander type retro video game, written in Zig for the WASM-4 fantasy console. Play on the web, or try out the native apps! ✨
Development
Make sure you have the latest (<code>master</code> branch) of <a>Zig</a> installed, as well as <a>w4</a> and <a>Just</a>. Then, run the following commands:
<code>shell
just # Build the project to a Wasm cartridge
just run # Run the game in a browser
just run-native # Run the game in the native runtime
just watch # Run the game in a browser, rebuilding on code change
just bundle # Create HTML, Windows, macOS, and Linux release artifacts
just clean # Clean all generated files</code>
To format code automatically, run the command:
<code>shell
zig fmt .</code> | []
|
https://avatars.githubusercontent.com/u/85013114?v=4 | Walker-00 | Walker-00/Walker-00 | 2021-05-29T08:35:27Z | စောက်ကြီး စောက်ကျယ်မပြောပဲ စောက်ကြီး စောက်ကျယ်တွေလုပ် | main | 0 | 1 | 0 | 1 | https://api.github.com/repos/Walker-00/Walker-00/tags | - | [
"c",
"computer-science",
"embedded",
"fullstack",
"low-level",
"rust",
"wtf",
"zig"
]
| 29,244 | false | 2025-05-21T18:29:41Z | false | false | unknown | github | []
|
Hi 👋, I'm Linus Walker
16y.o Computer Science Engineer with 6 years of experience from Burma
#
- My name is Linus Walker ( Rissk ).
- I'm 16 years old Computer Science Engineer with 6 years of experience from Burma.
- Founder And CEO Of [Null-Gate](https://github.com/Null-Gate) And [KarGate](https://github.com/Null-Gate/trunk)
- I do like low level system more than high level things.
- But I learn both and almost everythings like ML, Embedded, Web, Software etc...
- I've Deep Understanding Of Computer Science And STEM Stuffs.
- Rust, C and Zig are my Fav Langs.
- Dream: Wanna build a Free and Open Source Education organization call *FOSE* And Get Paid As You Learn Education.
- Fun Fact ```I've allergies with designing things.```
## My OS Choices
[](https://skillicons.dev)
## Language Skills
[](https://skillicons.dev)
## Other Skills
[](https://skillicons.dev)
#
#
[](https://github.com/ashutosh00710/github-readme-activity-graph) | []
|
https://avatars.githubusercontent.com/u/63668822?v=4 | injected_fields | ArborealAnole/injected_fields | 2022-01-25T12:10:59Z | injected_fields concept, a form of Explicit Management of Implicit Context (EMIC) | main | 0 | 0 | 0 | 0 | https://api.github.com/repos/ArborealAnole/injected_fields/tags | CC0-1.0 | [
"dependency-injection",
"emic",
"field-injection",
"implicit-parameters",
"implicits",
"object-oriented-programming",
"parameter-injection",
"zig"
]
| 56 | false | 2022-01-26T12:44:31Z | false | false | unknown | github | []
| injected_fields
Injected fields is a possible feature for Zig or any programming language; usage is given in <code>injection.zig</code>. Associated with the feature are two auxiliary features called <code>tenum</code> as described in <code>tenums.txt</code>, and <code>Access</code> as described in <code>Access.txt</code>. These two features are not necessary for injected fields, e.g. if strings are used to specify field access (see <code>stringly.zig</code>, a previous idea).
Motivation
<ul>
<li>separation of context provision logic from application logic</li>
<li>easier modification of structure context requirements or options without requiring modification of all callsites</li>
<li>decreased clutter from non-"volatile"/context-type parameters; decreased chance of accidentally changing an argument that is required to be the same through different function calls (such as a <code>std.mem.Allocator</code> in <code>std.array_list.ArrayListUnmanaged</code>)</li>
<li>managed container with the same code and flexibility as unmanaged container</li>
<li>easier delegation of tasks to sub-structure methods without need for excessive parameters or redundant physical pointer fields </li>
</ul>
Synopsis
```zig
const TrainNetwork = struct {
const Resources = struct {
using a: *Allocator,
};
resources: Resources,
};
const TransportationAuthority = struct {
// hidden parameter injections required (1 <em>Allocator):
pub fn at(self: </em>TransportationAuthority, i: u3) TrainNetwork {
return self.t[i];
}
};
const A = struct {
a: Allocator
@providing(@fields(A)...b...at()...resources...a),
b: TransportationAuthority,
};
```
Description
Injected fields (aka <code>using</code> fields) seem similar to "dynamic scoping" <a>[1]</a>; "implicit parameters" similar to as in Scala 2 <a>[2]</a>, Zig <a>issue #1286</a>; "givens" <a>[3]</a> in Scala 3; "dependency injection"; or "Explicit Management of Implicit Context (EMIC)" <a>[4]</a>. They are explicitly configured in an OOP pattern.
A struct may have a <code>using</code> field, which is "virtual" in the sense that it does not actually exist in memory representation of the struct. Rather, this field is required to be provided by configuration in a program that contains instances of the struct. Any parent structure using it can be configured to provide the field.
There must be exactly 1 candidate injection argument for every <code>using</code> field or else it is a compile error.
The compiler automatically injects the provided value as arguments/parameters through the necessary function calls. If you somehow get a pointer to an instance of a struct with the <code>using</code> field, then the compiler can automatically obtain the correct value for that field.
The <code>using</code> fields are always pointers, because they do not have physical storage but refer to an object stored elsewhere. Technically, they could be available on the stack because they are implemented as parameters, but this would be misleading because mutation would not be persistent. So there is an implicit address-of operation for the builtin functions.
If you want to provide a more complex way of obtaining the correct resource, e.g.
- you can call a function on (or method of) the injected field at the use-site.
- you can create an intermediate struct that is stored e.g. on the stack, which obtains with a function call the resource into a field that is <code>@providing()</code> for the use-site.
Strictly speaking there seems to be an aspect of parameter injection and an aspect of to-above field aliasing here. Zig <a>issue #7311</a> seems to be proposing to-below field aliasing limited to one level down.
Unused injected fields are allowed, just as not using a physical field is allowed. Not a strong requirement.
Benefits
<ul>
<li>simplicity</li>
<li>increases focus on "volatile" parameters (not in the RAM sense)</li>
<li>maps a field or declaration to a field; so does not cause hidden control flow, only augments explicit control flow in a hidden manner</li>
<li>equalizes the ease of unmanaged structures to that of managed structures, which was made easy with similarly "hidden" resource/context usage by the OOP pattern</li>
<li>in one sense the semantics of injected context parameters is more accurate than that of passing contexts through several function calls, because those function calls are often inlined by the compiler</li>
<li>easier to optimize allocator organization, adapt it incrementally. easy to provide allocators of different types to satisfy different requirements (random access (hugepages useful), sequential access (smaller pages ok), short usage period (arena-type), etc.), merge arena-type allocations with similar usage period. or to ignore that detail until it is useful to optimize it, but not later have extra hassle when it is.</li>
</ul>
For the last point, a simple example is if you create a <code>struct</code> that either uses its own allocator field or uses the <code>std.heap.page_allocator</code>. If you ever want to change it to use a provided allocator that is not stored within the struct, you will have to modify every method that uses the allocator, and every callsite.
Drawbacks and counterarguments
<ul>
<li>complexity</li>
<li>too many hidden parameters passed too deeply in non-inlined function calls</li>
</ul>
I think the compiler can optimize it by passing the hidden parameter through a static memory location, or single-purpose stack if there are deep non-inlined function call origin possibilities (like using "globals" but in a compiler-enforced correct fashion).
<ul>
<li>not a significant optimization vs. physical fields for <code>struct</code>s on the stack, given compiler optimizer</li>
<li>perhaps language feature is not necessary (simulation with metaprogramming)</li>
<li>less obvious which function calls use a resource at callsites for e.g. currently unmanaged containers that switch to <code>using</code> fields</li>
</ul>
However, the last point is not a fundamental difference from the possibilities in the current language, because any struct that you utilize in your program currently, however deeply in a struct hierarchy, could have e.g. an <code>Allocator</code> field or declaration that uses a default allocator without even taking one for a constructor. You would not currently see it using resource parameters in the function call chain. This feature could actually reduce hidden resource usage by increasing the appeal of unmanaged (but managed-like) structures, where at least the resource usage is declared higher in the struct hierarchy. | []
|
https://avatars.githubusercontent.com/u/16837066?v=4 | advent | Kornelijus/advent | 2021-12-01T03:52:15Z | 🎄 My solutions for Advent of Code, including previous years | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/Kornelijus/advent/tags | - | [
"advent-of-code",
"advent-of-code-2021",
"go",
"golang",
"python",
"rust",
"zig"
]
| 46 | false | 2022-12-05T21:04:28Z | false | false | unknown | github | []
| 🎄 Advent of Code
My solutions for Advent of Code, including previous years, for trying out languages new to me. | []
|
https://avatars.githubusercontent.com/u/18217298?v=4 | rtiow | yhamdoud/rtiow | 2021-12-10T15:34:43Z | A Zig implementation of Ray Tracing in One Weekend. | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/yhamdoud/rtiow/tags | MIT | [
"graphics",
"ray-tracing",
"raytracing",
"zig"
]
| 71 | false | 2021-12-20T15:04:17Z | true | false | unknown | github | []
| Ray Tracing in One Weekend using Zig
This is a Zig implementation of <a><em>Ray Tracing in One Weekend</em></a> by Peter Shirley.
The structure of the path tracer roughly follows the book, using idiomatic Zig constructs when possible.
Notably, the usage of runtime polymorphism in the material system is substituted with tagged unions.
Some other additions of my own include rendering the results to a window using OpenGL and multithreading.
Dependencies
<ul>
<li>Zig 0.9.0</li>
<li>GLFW</li>
<li>Glad (vendored)</li>
</ul>
Building
<code>$ zig build run -Drelease-fast=true</code> | []
|
https://avatars.githubusercontent.com/u/22677068?v=4 | zig-gitpod-template | markfirmware/zig-gitpod-template | 2021-04-01T15:09:11Z | Develop a zig project using gitpod.io | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/markfirmware/zig-gitpod-template/tags | MIT | [
"cloud",
"gitpod",
"ide",
"vscode",
"zig",
"zig-language-server"
]
| 2 | false | 2021-04-15T18:47:48Z | false | false | unknown | github | []
| zig-gitpod-template
Template repo for <a>zig</a> projects with <a>gitpod</a> support.
The easiest way to use gitpod is to install its browser extension.
Then instantiate this template repo and press the gitpod button.
(You will need to authorize gitpod access to your github account.)
The .gitpod.yml file will install the latest zig, zls, and vscode tools when the gitpod workspace is created.
Each time the workspace is started, the project will be built and run. If there is no build.zig file then a project will be created using zig init-exe. | []
|
https://avatars.githubusercontent.com/u/9872969?v=4 | hang-os | boricj/hang-os | 2022-02-01T18:12:35Z | An educational operating system whose development was pledged while drunk at a bar. | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/boricj/hang-os/tags | - | [
"aarch64",
"operating-system",
"zig"
]
| 19 | false | 2022-02-21T16:15:47Z | true | false | unknown | github | []
| HangOS 🥴
<em>An educational operating system whose development was pledged while drunk at a bar.</em>
How do I build this?
See the <a>HangOS build instructions</a>.
How do I run this?
See the <a>HangOS run instructions</a>. | []
|
https://avatars.githubusercontent.com/u/68767503?v=4 | programming-language-examples | ThomasRettig/programming-language-examples | 2022-01-16T13:22:13Z | A tiny collection of sample programs written in various programming languages, used to exhibit the various syntactical features of the language. | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/ThomasRettig/programming-language-examples/tags | - | [
"ada",
"d",
"elm",
"go",
"haskell",
"lisp",
"nix",
"pascal",
"perl",
"programming-language",
"programming-languages",
"r",
"vala",
"xaml",
"zig"
]
| 23 | false | 2022-02-07T01:54:37Z | false | false | unknown | github | []
| Progamming language examples
A tiny collection of programs written in various programming languages with a deliberate focus on the lesser-known. The goal is to illustrate the syntax of each language. The samples come from different sources; most are from Wikipedia.
Current languages
<ul>
<li>Ada</li>
<li>Elm</li>
<li>Vala</li>
<li>Haskell</li>
<li>Zig</li>
<li>Lisp</li>
<li>Perl</li>
<li>D</li>
<li>R</li>
<li>XAML</li>
<li>Nix</li>
</ul> | []
|
https://avatars.githubusercontent.com/u/28556218?v=4 | vpkz | joachimschmidt557/vpkz | 2021-08-15T13:33:11Z | Zig library and command-line application for working with Valve VPK files | trunk | 0 | 0 | 0 | 0 | https://api.github.com/repos/joachimschmidt557/vpkz/tags | MIT | [
"zig",
"zig-package"
]
| 36 | false | 2025-03-14T11:07:30Z | true | true | 0.14.0 | github | []
| vpkz
A zig library and CLI application for handling Valve VPK files
Works with Zig 0.14.0.
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> reading VPK headers
<br/><input type='checkbox' class='w-4 h-4 text-green-500 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' checked disabled></input> extracting complete archives
<br/><input type='checkbox' class='w-4 h-4 text-blue-600 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' disabled></input> selectively reading/extracting files
<br/><input type='checkbox' class='w-4 h-4 text-blue-600 bg-gray-100 border-gray-300 rounded focus:ring-blue-500 dark:focus:ring-blue-600 dark:ring-offset-gray-800 focus:ring-2 dark:bg-gray-700 dark:border-gray-600' disabled></input> creating/updating VPK files | []
|
https://avatars.githubusercontent.com/u/13890741?v=4 | rito_stats_zig | ZNielsen/rito_stats_zig | 2021-03-29T04:59:46Z | Grab stats with the Riot API | main | 0 | 0 | 0 | 0 | https://api.github.com/repos/ZNielsen/rito_stats_zig/tags | - | [
"zig"
]
| 5 | false | 2021-03-30T02:44:00Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/5464072?v=4 | aoc2021 | nektro/aoc2021 | 2021-12-01T11:25:44Z | Advent of Code 2021 | main | 0 | 0 | 0 | 0 | https://api.github.com/repos/nektro/aoc2021/tags | MIT | [
"advent-of-code",
"advent-of-code-2021",
"zig"
]
| 72 | false | 2021-12-15T07:56:16Z | true | false | unknown | github | []
| Advent Of Code Zig 2021
This repo provides my implementation for Advent of Code using Zig for 2021. It contains a main file for each day, a build.zig file set up with targets for each day, and Visual Studio Code files for debugging.
This repo tracks the master branch of Zig, <em>not</em> 0.8.1. It may not work with older versions.
This repo is built with Zig <code>0.9.0-dev.1815+20e19e75f</code>.
How to use this:
The src/ directory contains a main file for each day. Put your code there. The build command <code>zig build dayXX [target and mode options] -- [program args]</code> will build and run the specified day. You can also use <code>zig build install_dayXX [target and mode options]</code> to build the executable for a day and put it into <code>zig-out/bin</code> without executing it. | []
|
https://avatars.githubusercontent.com/u/48218838?v=4 | piwoscript | g3rwy/piwoscript | 2022-01-25T21:16:39Z | Experimental language with Polish keywords, that have mutliple backends and is also kinda a joke | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/g3rwy/piwoscript/tags | - | [
"esolang",
"piwo",
"polish-language",
"zig"
]
| 900 | false | 2024-12-16T14:45:52Z | true | false | unknown | github | []
| 404 | []
|
https://avatars.githubusercontent.com/u/8085910?v=4 | flipcase | Costava/flipcase | 2021-07-14T03:31:21Z | null | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/Costava/flipcase/tags | 0BSD | [
"ascii",
"zig"
]
| 4 | false | 2022-02-09T00:15:54Z | true | false | unknown | github | []
| flipcase
The program reads an ASCII or UTF-8 stream of bytes from stdin
and outputs the bytes to stdout while flipping the case of a-z and A-Z letters.
Tested with zig 0.9.0 and javac 1.8.0
Build with <code>make all</code>
Run tests with <code>make test</code>
License
BSD Zero Clause License. See file <code>LICENSE.txt</code>.
Contributing
Not currently accepting contributions. Feel free to open an issue. | []
|
https://avatars.githubusercontent.com/u/96973604?v=4 | zpp-crc32c | zpplibs/zpp-crc32c | 2022-01-04T11:32:21Z | crc32c lib for zig | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/zpplibs/zpp-crc32c/tags | Apache-2.0 | [
"crc",
"crc32",
"crc32c",
"zig"
]
| 16 | false | 2022-02-16T05:25:04Z | true | false | unknown | github | []
| zpp-crc32c
<a>crc32c</a> lib for zig
Usage
```zig
const crc32c = @import("zpp-crc32c");
const hello_checksum = crc32c.value("hello");
// extend
const helloworld_checksum = crc32c.extend(hello_checksum, "world");
```
Building
Fetch deps
<code>sh
git submodule update --init</code>
Build
<code>sh
./build.sh</code>
Run
<code>sh
./build.sh run -- hello world
./build.sh run-c -- hello world</code>
Run the tests
<code>sh
./test.sh</code>
Dist (cross-compilation)
<code>sh
./build.sh dist</code>
Release
<code>sh
./build.sh dist VERSION GITHUB_TOKEN</code>
Clean
<code>sh
./build.sh clean</code>
Tag
<code>sh
./build.sh tag v$VERSION</code> | []
|
https://avatars.githubusercontent.com/u/294603?v=4 | ArtificialLifePlayground | LordSk/ArtificialLifePlayground | 2022-01-17T16:36:23Z | Implementation of Dave Ackley's artificial life demo in zig | main | 0 | 0 | 0 | 0 | https://api.github.com/repos/LordSk/ArtificialLifePlayground/tags | - | [
"artificial-life",
"generative-art",
"zig"
]
| 107,378 | false | 2022-03-07T15:42:39Z | true | false | unknown | github | []
| Artificial life playground
This is a reproduction of the demo presented by Dave Ackley:
<a></a>
Goals
<ul>
<li>✅ Discover the zig programming language</li>
<li>✅ Implement a more performant version of Dave Ackley's demo</li>
</ul>
TODO
<ul>
<li>✅ Efficient sprite renderer (1M+ at 144+Hz)</li>
<li>✅ Dear ImGui integration</li>
<li>✅ Camera controls</li>
<li>✅ "Lifeform" logic</li>
<li>✅ Export to image</li>
<li>Mutating herbivore logic</li>
</ul>
Results
Video demonstrating plants, zaps and herbivores:
<a></a>
After implementing mutating plants I discovered I accidently made some kind of art generator, here are some results:
| []
|
https://avatars.githubusercontent.com/u/5728002?v=4 | IsRunning-Zig | batiati/IsRunning-Zig | 2021-10-11T23:22:39Z | IsRunning is a very simple and lightweight Windows command-line utility to check if some processes are running or not. | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/batiati/IsRunning-Zig/tags | Unlicense | [
"command-line-tool",
"docker",
"kubernetes",
"readiness-probe",
"windows",
"zig"
]
| 6 | false | 2024-10-08T18:47:55Z | true | false | unknown | github | []
| IsRunning
IsRunning is a very simple and lightweight Windows command-line utility to check if some processes are running or not.
It expects a list of process's names as argument and simply exits with code <code>0</code> if they were found, or <code>1</code> otherwise.
No output or message is printed.
Usage:
<code>CMD
IsRunning.exe PROCESS_1 [PROCESS_2] [PROCESS_N]</code>
<em>Examples</em>
<code>CMD
C:\> IsRunning.exe traefik.exe
C:\> echo %errorlevel%
0</code>
<code>CMD
C:\> IsRunning.exe traefik.exe node.exe
C:\> echo %errorlevel%
0</code>
<code>CMD
C:\> IsRunning.exe dead.exe
C:\> echo %errorlevel%
1</code>
Motivation
Its main purpose is to serve as readiness probe for containers that spawn multiple processes.
For example, a <a>Pod readiness probe</a> to detect if <code>traefik</code> is running:
<code>yaml
readinessProbe:
exec:
command:
- C:/IsRunning.exe
- traefik.exe
failureThreshold: 3
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 5</code>
<blockquote>
It's not advisable to run multiple processes on a single container, but for many reasons, it's not uncommon, especially for legacy applications in Microsoft Windows containers.
</blockquote>
Why not use batch script?
I used to use a batch script combining <code>tasklist</code> and <code>find</code> together:
<code>CMD
C:\> tasklist | find "traefik.exe"
C:\> echo %errorlevel%
0</code>
It works, but it's not the most efficient solution, particularly when you call it every 5 seconds for hundreds of containers.
This utility saves a little bit of CPU and memory by removing the overhead of <code>CMD</code> interpreter and all the string processing between <code>tasklist</code> and <code>find</code>.
This utility is implemented in <a>Zig</a>, just because we needed a native, small, fast, and secure binary to perform such task.
Limitations
<ul>
<li>
Windows only application
</li>
<li>
It is optimized for low memory consumption, and only works with ASCII processes names.
</li>
</ul>
Please, feel free to open an issue or send a PR if you might improve this implementation in some sense. | []
|
https://avatars.githubusercontent.com/u/54106488?v=4 | ay-arg | iddev5/ay-arg | 2021-08-18T11:13:19Z | Stupid simple command line argument parser in ZIg | master | 0 | 0 | 0 | 0 | https://api.github.com/repos/iddev5/ay-arg/tags | MIT-0 | [
"argument-parser",
"zig"
]
| 25 | false | 2024-07-06T16:09:49Z | true | false | unknown | github | []
| ay-arg
Stupid simple argument parser in Zig for basic uses.
<ul>
<li>Supports long argument types <code>--foo</code></li>
<li>Inkey and separate values <code>--foo=123</code> and <code>--foo 123</code></li>
<li>Short arguments <code>-s -i=1 -j 10</code> with values</li>
<li>Chaining arguments <code>-shj10</code></li>
<li>Positional arguments when no key is present or after <code>--</code></li>
</ul>
Example
demo.zig:
```zig
const std = @import("std");
const AyArgparse = @import("AyArgparse.zig");
pub fn main() !void {
const allocator = std.testing.allocator;
<code>var args = try std.process.argsAlloc(allocator);
defer allocator.free(args);
const params = &[_]AyArgparse.ParamDesc{
.{ .long = "foo", .short = "e", },
.{ .long = "test", .short = "s", .need_value = true, },
};
var argparse = AyArgparse.init(allocator, params[0..]);
defer argparse.deinit();
try argparse.parse(args[1..]);
var iter = argparse.arguments.iterator();
while (iter.next()) |entry| {
const k = entry.key_ptr;
const v = entry.value_ptr;
std.debug.print("{s} = {s}\n", .{ k.*, v.* });
}
for (argparse.positionals.items) |item| {
std.debug.print("{s}\n", .{ item });
}
</code>
}
```
License
This project is licensed under MIT No Attribution License.
See <a>LICENSE</a> for more info. | [
"https://github.com/iddev5/scafetch"
]
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.