Replies: 1 comment 6 replies
-
|
Yeah, it's something we plan on doing. We're planning on providing a C library that can be used instead of talking to a child process. Our bindings for Swift and Go both talk to Pkl by spawning a child process right now, but they're implemented in a way so that we can swap it out with a C library pretty easily (once it's ready). |
Beta Was this translation helpful? Give feedback.
-
|
+1 on guidance for building new bindings. |
Beta Was this translation helpful? Give feedback.
-
|
+1! I would definitely be interested in contributing to bindings for python. |
Beta Was this translation helpful? Give feedback.
-
|
Agree; we'll provide something here! |
Beta Was this translation helpful? Give feedback.
-
|
@bioball I hope that there's instructions for both the current (subprocess) and library (when built) mechanisms; by and large, I think that prototyping and shipping initial versions with subprocess support (sort of like LSP) is going to be much faster than using C bindings. |
Beta Was this translation helpful? Give feedback.
-
|
Here is our documentation for language bindings: https://pkl-lang.org/main/current/bindings-specification/index.html |
Beta Was this translation helpful? Give feedback.
-
Are there any plans to add C, c++ or similar abi bindings or generation for pkl? A shared wrapper around the go support might be sufficient, but it would greatly help with usage for not just those languages but binding python for example.
Beta Was this translation helpful? Give feedback.
All reactions