Giter Site home page Giter Site logo

Comments (5)

helmesjo avatar helmesjo commented on June 2, 2024 1

I see. In my case I'm just wrapping up glaze to do serialization/deserialization, and if something fails (however it can fail) I return my own parse_error consisting of error_code and msg. So I guess however much or little context can be given by glaze, it'd be nice if the same format_error() method can be reused (makes it easier to handle in generic code).
IMO it's totally fine if it just says "binary read error" and "binary write error" for the time being.

from glaze.

helmesjo avatar helmesjo commented on June 2, 2024 1

You're a trooper, thanks!

from glaze.

stephenberry avatar stephenberry commented on June 2, 2024

I was thinking about this the other day and I do think more information should be given about the error context for binary parsing. However, binary parsing errors should be extremely rare and not relied upon. I just added a warning comment about binary error checking to the documentation here.

Binary should not be written by hand and checksum mechanisms should be employed when sending across a network (or use protocols like TCP). The only way you would have parsing errors is if higher level validation and security mechanisms were broken or the code itself had errors (which is checked via unit testing). I have been adding more read parsing validation, but I'm undecided whether I should test all corner cases, because it causes a drop in performance for tests that shouldn't be needed if proper higher level safety mechanisms are used.

from glaze.

stephenberry avatar stephenberry commented on June 2, 2024

If you have an open API then you would need full checking, so I guess I'm convinced that there should be checks for all corner cases, except that some should be able to be turned off when used in a closed loop.

from glaze.

stephenberry avatar stephenberry commented on June 2, 2024

I've merged in support for your primary request. You can now handle parse_error using buffers of std::byte. The buffer context isn't given, but the index of the error is provided. The biggest benefit is that you can use glz::format_error for both binary and json.

from glaze.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.