asmble

Sorry I did not read it properly, you can use these ones instead to actually write WASM. https://github.com/WebAssembly/wabt https://github.com/cretz/asmble

It's not done here, but I've had success returning/accepting pointers over the Rust/JS boundary [0] using Box w/ raw pointers and mem::forget as necessary. They are just JS ints to places in the mem array like the mem refs in this blog. This can help you not require the "Cpu" instance as a static singleton but instead instantiate it as needed. 0 - https://github.com/cretz/asmble/blob/master/examples/rust-re...

The thread's a bit old, but I'll reply anyways. > Scala, Ceylon, Clojure provide their own stdlibs. On top of the JVM ones when targeting the JVM. E.g. java.lang.String (Kotlin too) > You can write non-OOP programs in Java bytecode Everything is still an object and all code is in methods. There is no way around that. Also, there are many other things like forced GC and what not that marry the bytecode to certain paradigms. > it's about ensuring that if someone claims they run Java bytecode, they actually can run it. And about their impls of java.lang and other base packages. And a way to make sure that licenses that Oracle doesn't like, such as non-OpenJDK-derived open source stdlib impls, are not given the tests. Other languages with compat tests publish them for all and yet aren't worried about losing their name. This is dangerous reaso

In many ways, the JVM bytecode is a superset of WASM. That's why I wrote https://github.com/cretz/asmble.

> IMHO WebAssembly solves that better but I also need to admit that they could already learn from Java. While that may be true of the language Java, WebAssembly's jump instructions are not without their annoyances too. For example, the JVM bytecode requires your stack to be precise when jumping, WebAssembly just cares about the most recent piece. If you expect your jump targets to have the same stack layout, WebAssembly makes the impl handle it. I had to account for this and other differences in my compiler [0]. 0 - https://github.com/cretz/asmble#control-flow-operations

No [0], and no in the other direction [1] (disclaimer, I'm the author of the latter) 0 - https://github.com/konsoletyper/teavm 1 - https://github.com/cretz/asmble

I am a pretty big fan, but for non-Android contexts I still like Scala better for a ton of reasons. I wrote a large Kotlin lib[0] the other day and documented a few annoyances[1] I had with it and the devs were very responsive (though non-devs seemed to pick apart maybe one or two of bullet points to dismiss the entire critique). In the future I would use Kotlin for any Android need (obviously) and any time where I wanted to be lighter weight than Scala. As for native/JS use, I am waiting on the multiplatform story to materialize more before I have a strong opinion, but I would still go with Scala for how easy it is to develop multiplatform libs/progs w/ JVM/native/JS where I can easily have platform specific pieces. Kotlin is almost there[2], but not quite yet. 0 - https://github.com/cretz/asmble 1 - https://gist.github.com/cretz/2a49514

Here are my string-to-sexpr [0] parser and sexpr-to-ast parser [1] for the text format. There are some oddities such as forward function names and the fact that the binary form doesn't have a lot of these shortcuts, but overall it is very straightforward. 0 - https://github.com/cretz/asmble/blob/e9cdfc3b0feafc3d4f76b9d... 1 - https://github.com/cretz/asmble/blob/e9cdfc3b0feafc3d4f76b9d...