errors
DISCONTINUED
GJSON
Our great sponsors
errors | GJSON | |
---|---|---|
30 | 34 | |
7,511 | 13,497 | |
- | - | |
0.2 | 5.2 | |
over 2 years ago | about 1 month ago | |
Go | Go | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
errors
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
- Error handling and serializing
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
-
My next client wants to redevelop a java Webapp with go
pkg/errors or stdlib errors - Error handling, but I wrote my own package for that tailored to my projects' needs. (FYI primalskill/errors but please don't use it as it's not production-ready yet and it will change a lot)
-
What are some good open source project to read when learning Go?
https://github.com/pkg/errors - errors with stack traces
-
Anyone using github.com/pkg/errors for stack traces?
The pkg.go.dev page lists 14k+ projects importing it, but the Github repository has been archived which would seem to discourage use. I'm also not a huge fan of the naming conflict with the stdlib errors package. The README notes it went into maintenance mode but it appears this, too, has passed.
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
The pkg/errors and xerrrors are not maintainted
GJSON
-
Rob Pike: Gobs of data (2011)
Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives.
By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]).
There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we just need to change the data a little.
--
1: https://github.com/alecthomas/go_serialization_benchmarks
2: https://github.com/golang/go/issues/29766#issuecomment-45492...
--
3: https://github.com/goccy/go-json
4: https://github.com/vmihailenco/msgpack
5: https://github.com/fxamacker/cbor
--
6: https://github.com/valyala/fasthttp#faq
--
-
Jj: JSON Stream Editor
I like jq, but jj is so fast it is my go-to for pretty printing large json blobs. Its parsing engine is available as a standalone google module, and I've used it in a few projects where I needed faster parsing than encoding/json:
```
I don't think there is a way to sort an array, though. However, there is an option to have keys sorted. Personally, I don't think there is much annoyance in that. One could just pipe `jj` output to `sort | uniq -c`.
-
Library to analyze an arbitrary JSON string
I’m using GJSON, so far so good!
-
Any way to convert unknown/dynamic json to generic object structure
https://github.com/tidwall/gjson is a relatively sensible library if this is something you need to deal with and the structure is actually unknowable.
- Need help with getting the grandchild in nested JSON
- Double down on python or learn Go
- Ad hoc JSON parsing
-
Ask HN: Why isn't JSON-RPC more widely adopted?
one way could be you peek method using sth like https://github.com/tidwall/gjson
-
Is there a way to parse unstructured data?
That’s because Go is a statically typed language. If you want to easily access the data, you need to know the structure, if you don’t know the structure, then you’re going to have to jump through hoops to get at the data. I would probably try using https://github.com/tidwall/gjson if I were you.
What are some alternatives?
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
go-json - Fast JSON encoder/decoder compatible with encoding/json for Go
intrinsic
zerolog - Zero Allocation JSON Logger
autoflags - Populate go command line app flags from config struct
gojson - Automatically generate Go (golang) struct definitions from example JSON
hub - A command-line tool that makes git easier to use with GitHub.
go-multierror - A Go (golang) package for representing a list of errors as a single error.
logrus - Structured, pluggable logging for Go.
ngrok - Introspected tunnels to localhost
bitio - Optimized bit-level Reader and Writer for Go.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library