FrankReh

I think you can think of this like a Go map. If you create the trie first in one goroutine, then you can use any number of goroutines for reading...

No problems. The whole design requires the slice of edges remain in sort order so it makes sense to take advantage of that when adding an edge. And there are...

Another alternative is to ignore any kind of error so the final attempt to use the shell to cd and pwd can play out. This would mirror the darwin case...

FYI. I followed this thread this morning and then found https://github.com/gopherjs/gopherjs/pull/959 which includes code for module handling (via a fastmod package) and a gopherjs implementation of reflectlite. I built from...

This was interesting. I can't offer a fix to the library but the code works if slashes are put before the names, so "/foo", "/bar", and "/baz" are created. Also,...

This error log to the console is going to happen each time a js.Value is converted to sting with the call String(). jsString manually calls finalizeRef because it is trying...

To help avoid any confusion for others finding this thread. The calling convention TinyGo uses, thanks to LLVM's IR calling convention I think, changes the arguments passed to the wasm...

I would still stand by my comment and code snippet from above. There is one place where the finalizeRef is called by the syscall/js.go file so it is a legitimate...

It could be confusing that tinygo hasn't been fixed to implement the js.finalizeRef callback in wasm_exec.js as I showed above could be done. The solution I showed above does help....

I'm assuming protobufs would be used for communication. What are the thoughts on the use model? One per machine, one per user logged in, or something else even more granular?...