FalsePattern
- Slovakia
- https://falsepattern.com
-
Writing java and zig spaghetti code in my free time
-
Joined on
2024年06月01日
zig build CLI flag to print path to the configuration file
I have a local prototype for this, i'll open a pr later today once i had time to tidy it up a bit.
Zig 0.17.0 build system rewrite compatibility
47d869ff27
docs: update readme
bd8b49e858
docs: update readme
d124a58ef2
docs: Add copyright and license info to every file
c0c02d77d9
init: import into VCS
Publish to Maven Central
358c884833
docs: add maven central notice to readme
9a4d6b928a
build: fix maven publish issue
41b7aee4d8
ci: 1.0.0
69e047d1b0
build: prepare for publishing
97ba1c0797
feat: drop minimum supported java version to java 17
bf625e7662
build: update gradle and dependencies
62b9e60133
feat!: Add full javadoc, remove lombok, and get the code ready for release in general
Remote Development support
anytype removal planning
See also: ziglang/zig#32099
Replace wasm hardcoupled api with factory pattern
Replace wasm hardcoupled api with factory pattern
No longer relevant, i decided to go with the full port route instead.
anytype -> anyval
db37f88557
feat: make created file permissions match zig-minisign
156f31d2d4
fix: File io test failures
fe989e458c
feat: Move exception codes out of api package, fix up cli api
0558f5f9a1
feat: Use atomic file replacement for key writes
6b02c06eb1
chore: clean up exception api, add usage example
39d41fd6a7
feat!: ditch wasm implementation, manually port zig-minisign to java