Originally created by @bioball on GitHub (Mar 3, 2025).
Truffle as of 0.24.1 uses native bindings for an optimized runtime. However, binding to a C library within a plugin is fraught; Pkl Gradle should ideally be using javaexec to call into Pkl to avoid any issues.
Originally created by @bioball on GitHub (Mar 3, 2025).
Truffle as of 0.24.1 uses native bindings for an optimized runtime. However, binding to a C library within a plugin is fraught; Pkl Gradle should ideally be using `javaexec` to call into Pkl to avoid any issues.
I actually think we should not do this. It adds at least a second overhead to every Pkl task. This is a lot, especially for things like the synthesized analyze imports task, which is an implicit task of every "normal" task.
Closing this.
@bioball commented on GitHub (Mar 6, 2025):
I have a WIP branch here: https://github.com/bioball/pkl/tree/gradle-javaexec
I actually think we should not do this. It adds at least a second overhead to every Pkl task. This is a lot, especially for things like the synthesized analyze imports task, which is an implicit task of every "normal" task.
Closing this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bioball on GitHub (Mar 3, 2025).
Truffle as of 0.24.1 uses native bindings for an optimized runtime. However, binding to a C library within a plugin is fraught; Pkl Gradle should ideally be using
javaexecto call into Pkl to avoid any issues.@bioball commented on GitHub (Mar 6, 2025):
I have a WIP branch here: https://github.com/bioball/pkl/tree/gradle-javaexec
I actually think we should not do this. It adds at least a second overhead to every Pkl task. This is a lot, especially for things like the synthesized analyze imports task, which is an implicit task of every "normal" task.
Closing this.