What's the purpose in putting WASM/JS tools in "syscall/js"?

I’d imagine that since the “syscall” package is deprecated that we would not want to encourage it’s use. Putting the WASM JavaScript utilities in “syscall/js” rather than “x/sys/js” seems counter-intuitive to me. Was there a reason for this?

Typically, because it’s needed by the standard library.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.