New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deserializing untagged enum variants broke/changed between v1.0.38 and v1.0.39 #1216
Comments
Can you share the enum that broke? Is there a custom Deserialize impl involved? |
Sure! Sorry, got a little lost in trying to get cargo to use my local serde. I wanted a way to reference another file from inside of a TOML file, so I made this. As an aside, if there's a more idiomatic way to do this with serde, I'm all ears. |
I think the trouble is because TOML represents bytes as an array of integers (playground) rather than a string -- so when the Deserialize impl calls Some unrelated suggestions:
|
Thanks for the feedback, very much appreciated! The bound attribute was required when I first wrote this, but I guess that requirement is gone? Weird. I'd still say this is a bug, since the behavior changed pretty dramatically for a patch version, no? |
Absolutely. Thanks! This is fixed in 3c4961c and released in Serde 1.0.40 so the code in the gist is back to working as before. Really sorry about the breakage. |
Still working out the details, but something changed between 1.0.38 and 1.0.39 that's broken my untagged enum.
I'm doing a bisect right now to figure out the commit that introduced the change.
The text was updated successfully, but these errors were encountered: