-
Notifications
You must be signed in to change notification settings - Fork 1.2k
go-yaml is archived, migrate to goccy/go-yaml #3667
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
Comments
Yeah, I'm not entirely sure. |
goccy/go-json and goccy/go-yaml follow very different design philosophies. goccy/go-json aims to accelerate JSON handling while preserving the encoding/json-compatible API. To achieve that speed-up it relies heavily on the unsafe package, which makes running it in production quite risky. goccy/go-yaml was created to solve the issue of go-yaml/yaml.
In addition, goccy/go-yaml passes more YAML test suites than go-yaml/yaml. And goccy/go-yaml is already used in several large projects. That said, I agree it’s prudent to evaluate other YAML packages as well, so opening a window to collect alternative candidates sounds like a good plan. |
@sonatard Ok, I took I'm not able to devote the time to move gqlgen over to it right now, but I would love to have any PRs if you or someone else is able to devote the time to that. |
go-yaml/yaml is archived. migrate to goccy/go-yaml
migrate in gqlgenc.
Yamashou/gqlgenc#277
The text was updated successfully, but these errors were encountered: