-
Notifications
You must be signed in to change notification settings - Fork 30
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
Implement Encode/Decode for CString #24
Comments
Yeah, I haven't added back all the features bitcode 0.5 supported CString being one of them.
This is only imposed on the Encoder, not the actual type. I think the error message is misleading.
I eventually want to add missing types, but this seems like the best option for now. |
Thanks. I do have one minor minorly related questions if you don't mind. I can't find serde support for serializing with existing buffers, which makes the serde-based benchmarks much slower than they should be since they'd have to allocate. Has this been removed? |
Yes for a rather complex reason. Bitcode 0.6 encoding converts any type to a
|
All right, so I'll put the serde-based tests in a separate category too :) I'm guessing then this also extends to fields marked with |
This is blocked on determining the serialized representation.
|
I've updated bitcode, and if you try and build the musli test suite right now like this:
You get the following errors
Overall the errors are a bit of a red herring, but first it seems like CString just isn't supported. Second it seems like you might be imposing a
Send + Sync
bound which might not be necessary (or at least I don't see why it should be!).If you don't want to add
CString
support I can carve out a separate category for bitcode derive in my tests.Thank you!
The text was updated successfully, but these errors were encountered: