We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hi, you've mentioned kcl in this blog posting https://moonrepo.dev/blog/moon-v1.29 and that it has no rust binding. im pretty sure that that's not true as kcl is written itself in rust. the lib can be found here: https://github.com/kcl-lang/lib/tree/main/src the docs for it here: https://www.kcl-lang.io/docs/reference/xlang-api/rust-api
i haven't found a way to comment on the blog post so im writing it here. sry if this is the wrong place.
The text was updated successfully, but these errors were encountered:
They would need to publish it to crates.io to be usable.
Sorry, something went wrong.
as a non rust developer i don't get it. why isn't cargo add --git https://github.com/kcl-lang/lib good enough?
cargo add --git https://github.com/kcl-lang/lib
@thelittlebug Because the config library schematic is published to crates.io and you can't depend on deps that also aren't published to crates.io.
No branches or pull requests
hi, you've mentioned kcl in this blog posting https://moonrepo.dev/blog/moon-v1.29 and that it has no rust binding.
im pretty sure that that's not true as kcl is written itself in rust.
the lib can be found here: https://github.com/kcl-lang/lib/tree/main/src
the docs for it here: https://www.kcl-lang.io/docs/reference/xlang-api/rust-api
i haven't found a way to comment on the blog post so im writing it here. sry if this is the wrong place.
The text was updated successfully, but these errors were encountered: