The README suggests to use "https://github.com/zig-utils/zig-regex/archive/main.tar.gz" as the url and to then use the hash zig will provide. While this works locally as long as you keep your cache, this will fail on other machines since the hash will change together with changes in the main branch.
Users should target a release.
The problem with that however, is that the new release actually breaks compatibility with the current zig release (0.16.0), because of the usage of @backingInt which only exists on the master branch.
The README suggests to use
"https://github.com/zig-utils/zig-regex/archive/main.tar.gz"as theurland to then use the hash zig will provide. While this works locally as long as you keep your cache, this will fail on other machines since the hash will change together with changes in themainbranch.Users should target a release.
The problem with that however, is that the new release actually breaks compatibility with the current zig release (0.16.0), because of the usage of
@backingIntwhich only exists on themasterbranch.