Chris Heyes
Chris Heyes
Related: https://github.com/NostrGit/NostrGit/issues/115#issuecomment-1561512746
> Right now the plan is that all discussions will happen over nostr when NostrGit reaches v1.0. Any kind of bridging with current/legacy systems like GitHub comments will be future...
> but lord... GitHub... In a fashion the GitHub back-end would simply be an "implementation detail" of the relay, which can optionally be swapped out later for a sexy sovereign...
> There is no such thing as backend authentication If you ever want a to bridge to GitHub there is :) > every commits must be signed to ensure auth...
npub1h77jdhr42sx9a697prc0ltepjx5scclr0nsxvsfdyhx055gyuucq8gytje
Yes the build.zigs for samples were not intended to be run using zig build. Is there any benefit to doing this over just running a particular sample build command from...
> Oh I found another way to break the `Options` dep with an `anytype`: https://github.com/Pyrolistical/zig-gamedev/pull/2/files I think we should make this change. Sample apps only consume a self-defined subset of...
Repro'd with Zig 0.13.0-dev.211+6a65561e3
I think the fix for the macro redefinition error is to not define it: https://github.com/zig-gamedev/zig-gamedev/pull/616/commits/2f699d72e2b742efe6fb49cb1d6e1e843a8e77e1
This is cool. But I don't think we should merge it. I'd like to try and lean on Zig's incoming hot code reload features (https://github.com/ziglang/zig/pull/20580) and support all samples instead...