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

Explore gojq instead of linking to libjq #80

Open
jzelinskie opened this issue Jun 5, 2020 · 1 comment
Open

Explore gojq instead of linking to libjq #80

jzelinskie opened this issue Jun 5, 2020 · 1 comment
Labels
exploratory Research and opinions are needed

Comments

@jzelinskie
Copy link
Owner

gojq is a pure Go libjq implementation.
It does have documented incompatibilities, but it's worth leaving an issue open to see if the community is more interested in 100% compatibility or attempting to avoid the complication of linking against C.
@jzelinskie jzelinskie added the exploratory Research and opinions are needed label Jun 5, 2020
@jzelinskie
Copy link
Owner Author

We could potentially then support various backends if we fleshed out an Engine interface that could be implemented by both libjq and gojq. We could compile all engines into all binaries or allow users to build without cgo and only use pure Go engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
exploratory Research and opinions are needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jzelinskie