-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upstreaming plan #3
Comments
Sounds good! Personally I think doing 1. and 2. together would be OK as the implementation for |
Yeah I just want to avoid c&p churn in case there is still discussion on names and doc strings. (Working on this already took me much more time than I expected…) |
In the end did 1. and 2. together which is now merged. For reference here are all the PRs: |
I have now added tests. In
test.ml
we ensure that all uchars codec according to spec and a few other tidbits. Intest_long.ml
I have a longer test (~8min on my machine) that ensures we do not decode invalid byte sequences to any uchar, I don't think people want that in the test suite…In any case I think an upstreaming PR sequence could be:
Bytes
andUchar
with the codec.String
.Buffer
use theBytes
encoders.The day
Bigarray.Bytes
exists I'll happily make a PR to add them there aswell ;-)What do you think @gasche @nojb ?
P.S. I'll have to switch to something else in the upcoming days, I hope to be able to get back to it at latest by mid october.
The text was updated successfully, but these errors were encountered: