Jason Phan
Jason Phan
I'm getting that now too. Is that the correct behavior do you think or?
The problem is apparently inferred error sets. I guess you can't use them anymore when implementing methods that have `anytype` parameters? Making the error set explicit fixes this issue.
Relevant issue in the ziglang repo: https://github.com/ziglang/zig/issues/12806
I usually try to follow these rules: - Do what most people would expect, or whatever would serve as a reasonable default. - The value being serialized shouldn't be modified....
@polykernel, after thinking for a bit, I feel like serializing `EnumMultiset`s as maps (something like `{"enum_foo": 1}`, where `1` is the number of `enum_foo`s in the set) makes more sense....
Ahh okay, I haven't worked with multisets often so I wasn't aware that they're usually maps. I'll note that down in the original post.
This would be *very* helpful, indeed now that I think about it. However, Serde's able to avoid consuming tokens upon failure because it has a peek operation in its JSON...
update: A PR for a peek method in `std.json` has been made: https://github.com/ziglang/zig/pull/12798
v2 - Bumped Fedora version to 38 from 33
> I see there is a pull request to re-implement the script from bash to python. That's me! :D I didn't know about Dangerzone when I started but you've certainly...