Closed yichen88 closed 1 year ago
@yichen88 @sylvlecl This is normal, there is no way to compile Groovy code (exception code annotated with CompileStatic) because this is a dynamic language. This is why in the past months I made some refactoring in core repo to separate groovy code into dedicated and optional Maven modules. As it is, there is no way to run IAL script with a GraalVM compiled version of itools. If we want to do that, we should move to a statically compiled DSL similar to Groovy one: we can do that with Kotlin DSL. Maybe this is something to investigate? We also have the same question for dynamic simulation DSL.
Feature
Currently, I successfully created an itools native-image which could run
loadflow
command in graalvm. But after i created another image withaction-simulator
command(with 4 new config files), there is an issue about groovy dsl and graalvm AOT at runtime. I am not sure it could be done or not. Here is the error at image runtime:What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)