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

Return allocation error in deserialize instead of panicking #238

Merged
merged 1 commit into from Nov 9, 2020
Merged

Return allocation error in deserialize instead of panicking #238

merged 1 commit into from Nov 9, 2020

Commits on Nov 8, 2020

  1. Return allocation error in deserialize instead of panicking 

    There's no way to catch allocation errors since out of memory errors
cause an abort. Fail gracefully by returning the error instead of
panicking.
    @epilys
    epilys committed Nov 8, 2020
    Copy the full SHA
    d1394a0 View commit details
    Browse the repository at this point in the history