Viewing profile — mlugg

> OP handles the small change problem by hashing IR instead of source text OP here---I think you got confused somewhere, because this isn't true! The hashes we take are of source c…

Oh, I forgot to respond to the "corrupted binary" thing in my other reply, sorry. Right now, yep, corrupting the binary that the compiler reads would crash the compiler. In future,…

Zig uses a "single compilation unit" compilation model, so even if we did what you're suggesting, pretty much everything in the post would still be relevant, especially the whole-f…

It works through the fact that I specified "runtime" function ;) A bit after that quote I have a note about `inline` functions in Zig, where I mention that they perform semantic in…

That's there for translate-c, it's not used for compiling C code (To be clear, squeek502 is a part of the Zig core team [0], so he knows what he's talking about :D) [0]: https://zi…

It only works with our self-hosted code generation backends (the main one being for x86_64), which right now don't have any optimisation passes. It's planned that they will in futu…

Zig team member here---obviously I can't say for sure yet, but I'm pretty confident the number will be basically identical. In the Zig compiler, incremental updates (rebuilds) have…

Worth noting that while it's absolutely unfortunate that we're hitting this Forgejo design flaw, AGit honestly is just a better workflow, and I (Zig core team member here, full pus…

`u3` would be base 8, i.e. octal---I think you meant to use `[400]u6`? Aside from that: I'm not familiar with how standard base64 deals with endianness, so I'm not sure if it would…

Uh, no? My writing style just happens to include a lot of em-dashes, as is very common. And it's not like I'm pasting a weird Unicode codepoint all over the place, that's just (rig…

I appreciate the kind words :)

> The current interim plan... What do you mean by "interim"? As I explicitly stated in the comment you quoted, it has never , and likely will never, been planned for the Zig compil…

> the build for x86_64 Linux failed. Hm, are you referring to the CI failure on the x86_64-linux-release CI job on the current tip of master on the main Zig repository? That one's …

It is indeed (somewhat) related, and in fact that was fixed by this PR: https://github.com/ziglang/zig/issues/25771

Oh, no problem at all & no shade of any kind intended! I just wanted to clarify this point since it seems like a good few people got that misconception. That doesn't mean you can't…

Hi, author of this devlog here! Not to dismiss concerns about breaking language changes, but there seems to be a bit of a misconception here that this compiler change was highly br…

Zig team member here: we've migrated to Forgejo Actions [0], which is a system built into Forgejo (the Git forge used by Codeberg) which is very similar to GitHub Actions. In fact,…

I think this thread caused a bit of a hug of death; I too was seeing pretty bad page loads earlier today, but that seems to have sorted itself out. Understandable imo, because Code…

GitHub's API has extremely aggressive rate limits which make migrating large numbers of existing issues and PRs off of the platform borderline impossible. AIUI, this is why Gitea's…

Forgejo Actions is what Zig has migrated to. It's very similar to GitHub Actions; the downside of that is that you inherit questionable design choices, but the big upside is that m…

This is extremely misleading. "Membership" is about direct contribution to and influence over the non-profit; it'd be somewhat analagous to being a GitHub shareholder. The very fir…

This was the very first thing I noticed when we (the Zig team) started seriously trialing Codeberg. Honestly, the transition was worth it just for the ability to navigate the websi…

> This has been pointed out to them many times, and it's seemingly not something they're willing to fix. On the exact page you're on is a link to an issue [0] acknowledging that th…