←back to thread

Zig breaking change – Initial Writergate

(github.com)
228 points Retro_Dev | 5 comments | 04 Jul 25 04:11 UTC | HN request time: 1.019s | source
Show context
Aissen ◴[04 Jul 25 08:15 UTC] No.44462348[source]▶
This is why it's good to have automated tooling that can do semantic changes on your language and standard library use. Go has `go fix` even if it was only used in pre-1.0 days AFAIK. It is never lost because this type of tooling can be used as the foundation for linters, refactoring tools, etc. Is there such a solution in Zig?
replies(1): >>44463239 #
1. flohofwoe ◴[04 Jul 25 10:34 UTC] No.44463239[source]▶
zig fmt has some auto-fixes for upgrading source code to new Zig versions, AFAIK it's only for language changes, not stdlib changes though.
replies(1): >>44463635 #
2. Aissen ◴[04 Jul 25 11:39 UTC] No.44463635[source]▶
Nice, I wonder if adapting it for this change would make sense?
replies(1): >>44463701 #
3. throwawaymaths ◴[04 Jul 25 11:48 UTC] No.44463701[source]▶
its a really huge change
replies(1): >>44467047 #
4. Aissen ◴[04 Jul 25 19:05 UTC] No.44467047{3}[source]▶
Isn't that an argument for automated fixing?
replies(1): >>44467427 #
5. throwawaymaths ◴[04 Jul 25 20:01 UTC] No.44467427{4}[source]▶
huge in complexity. though looking at it i see andrew has made a "polyfill" ish thing to give ppl a way out for a ?(a few)? releases