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
I suggest a new FAQ entry e. g. dealing with ruby gems via ruby.wasm.
Now, I assume right now this is not possible - that is ok. Please mention it in the FAQ.
But ... let's assume that some gems are simple.
Like a hello world gem:
class HelloWorld
def initialize
end
def result?
'Hello world!'
end
end
So we can use the ruby.wasm .write() method onto result? (or any other
method name that is similar, this here is just an example).
Such code should work just fine. Just that it may be stored in a .gem file.
Is there a way to get support for that? In such a simple case we can probably
just embed the text (content of hello_world.rb) into the String that is evaluated,
so just File.read() should suffice. But I wonder whether there is some official
support for this via ruby.wasm. Many simple gems could be made to work
that way. (Of course other gems that are more complicated or require
Thread may not work, but perhaps in the future.)
The text was updated successfully, but these errors were encountered:
I suggest a new FAQ entry e. g. dealing with ruby gems via ruby.wasm.
Now, I assume right now this is not possible - that is ok. Please mention it in the FAQ.
But ... let's assume that some gems are simple.
Like a hello world gem:
So we can use the ruby.wasm .write() method onto result? (or any other
method name that is similar, this here is just an example).
Such code should work just fine. Just that it may be stored in a .gem file.
Is there a way to get support for that? In such a simple case we can probably
just embed the text (content of hello_world.rb) into the String that is evaluated,
so just File.read() should suffice. But I wonder whether there is some official
support for this via ruby.wasm. Many simple gems could be made to work
that way. (Of course other gems that are more complicated or require
Thread may not work, but perhaps in the future.)
The text was updated successfully, but these errors were encountered: