There’s a compiler error which has been blocking me from being able to update to the 0.15 changes. They’ve been fixed in the 0.15.x branch for over a month, but since there’s been no 0.15.2 release I haven’t been able to update. Specifically, the issue I’m encountering is that std.json.innerParseFromValue can’t be used with i64/u64 structs (Lossy int to float coercion on `std.json.innerParseFromValue` · Issue #24728 · ziglang/zig · GitHub).
Are there any plans for a 0.15.2 release? I’d really like to be unblocked from releasing a 0.15 version of my library, and updating my applications to 0.15.
5 Likes
0.15.2 milestone exists so it is planed. Also Andrew said:
After relanding the respective fixes for this and doing another round of Writer/Reader bug fixes, I think it’ll be time to tag 0.15.2 because master branch has now diverged quite dramatically from 0.15.x branch in terms of the compiler implementation, so cherry picking fixes has become more brittle
But it was already 18 days since that message so it’s difficult to say when it will happen.
11 Likes
It’s done now. I’ll make the tag as soon as the CI is green.
29 Likes
Thats interesting timing. Guess I’ll skip 0.15.2)
I’m guessing that’s from master branch? 0.15.2 doesn’t include the clang → aro translate-c changes.
4 Likes
Oh that’s great thanks. I completely forgot they are separate)
1 Like
Yep that’s the purpose of a patch release! Low risk, non-breaking bug fixes only 
We still have plenty of time to address the C translation breakage. @kcbanner has a nice PR up for example: Add error bundle support to `translate-c`, unify `cmdTranslateC` and `cImport` by kcbanner · Pull Request #25495 · ziglang/zig · GitHub
10 Likes
