Implement a compatibility layer for JSR 223

[andreaTP]

https://docs.oracle.com/javase/8/docs/technotes/guides/scripting/prog_guide/api.html

[thomasdarimont]

Support for JSR 223 sounds interesting!

I wonder how this should work though, given the fact that the Scripting API works mostly with Strings.

How should users provide wasm "scripts"?
Wasm as base64 encoded String, or should we interpret the script as a path to a wasm file?
Should we support .wat?

How should we specify which exported function to call? Should we default to the "start function".

How should we handle parameter bindings, e.g. enforcing their types?

[andreaTP]

Let me share my thoughts on this:

I would take inspiration from the API exposed by GraalVM Polyglot.

How should users provide wasm "scripts"?

byte[] ?

Wasm as base64 encoded String, or should we interpret the script as a path to a wasm file?

Why base64? Do you see any issue with using directly array of bytes?

How should we specify which exported function to call? Should we default to the "start function".

The start function will be invoked on initialization of the Module, we need to be able to extract the exported functions by String name.

How should we handle parameter bindings, e.g. enforcing their types?

We don't have this and the API is still not really stable there, I would leave it fully low level and dynamic at the moment and we will refine/improve at a later stage.