Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Non-validating deserialize #177

Closed
Tracked by #178
saik0 opened this issue Feb 5, 2022 · 0 comments · Fixed by #180
Closed
Tracked by #178

Non-validating deserialize #177

saik0 opened this issue Feb 5, 2022 · 0 comments · Fixed by #180

Comments

@saik0
Copy link
Contributor

saik0 commented Feb 5, 2022

I changed my mind while preparing for release. I still think the default should validate inputs, but we should offer an escape hatch that does not validate for deserialize heavy workloads from trusted sources.
This was referenced Feb 5, 2022
Open
Merged
@bors bors bot closed this as completed in 60ec7d2 Feb 7, 2022
not-jan pushed a commit to not-jan/roaring-rs that referenced this issue Aug 31, 2022
@bors @saik0
Merge RoaringBitmap#180
9748254 
180: add unvalidated deserialization r=Kerollmops a=saik0

Closes RoaringBitmap#177

Co-authored-by: saik0 <github@saik0.net>
Co-authored-by: Joel Pedraza <github@saik0.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add unvalidated deserialization saik0/roaring-rs
1 participant
@saik0