Playground

[danilopedraza]

I need to make a playground, so it is easy to try the language.

I looked at the code of Dart, Go and Rust playgrounds, and all of them run with a backend where all the code runs.

[danilopedraza]

I found a nice exception: Io. It has a REPL compiled in WASM.

[danilopedraza]

I'm going with the plan of compiling to WASM. However, this needs some preparation work.

• [x] Split core into smaller crates
• [x] Create builtins that interact with the browser instead of system calls

This will allow me to only compile to WASM what I need, and to interact with the browser in a non-hacky way.

[danilopedraza]

Splitting was not necessary. I used wasm-pack to generate the necessary wasm and it compiled only what was necessary.

[danilopedraza]

I'm using wasm-bindgen to generate all the glue code. Overall, this looks good.

[danilopedraza]

The playground now (barely) works. I need to work in the interface, ergonomics and error reporting (crashes, overflow)

[danilopedraza]

I just saw this tool, for the record.

[danilopedraza]

Here are some requirements for the playground:

• [x] The programmer should be capable of setting some standard input, so she can get it with the getln() function
• [x] The programmer should be capable of executing the code with a button in the screen and the Ctrl+Enter command, so it's possible and easy to execute the code
• [x] The programmer should be able to see errors related to memory without looking at the browser console, so he is aware of a possible cause for problems
• [x] The programmer should be able to see the code with its syntax highlighted, so it is easier to read and understand
• [x] The programmer should have easy access to the book, so she can get information on how to use the language