You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we could compile some Standard libraries into the native image Enso binary by default. Standard.Base is anyway closely coupled with the engine version, so having them both in a single binary shall not hurt much and the startup speed would increase in magnitudes.
What is needed?
find all polyglot java import statements in the library
register public method of such classes for reflection
make sure they are available in NI by writing a Feature
Slight drawback is related to #9129 - it is not going to be possible to pass instances of NI compiled library JARs to JVM loaded library JARs. The polyglot import would then be mostly internal, not exported.
The text was updated successfully, but these errors were encountered:
As an alternative approach to loading libraries via JVM while running the interpreter as native image binary
we could compile some
Standard
libraries into the native image Enso binary by default.Standard.Base
is anyway closely coupled with the engine version, so having them both in a single binary shall not hurt much and the startup speed would increase in magnitudes.What is needed?
polyglot java import
statements in the librarySlight drawback is related to #9129 - it is not going to be possible to pass instances of NI compiled library JARs to JVM loaded library JARs. The
polyglot import
would then be mostly internal, notexport
ed.The text was updated successfully, but these errors were encountered: