Michael Bebenita

Part of the reason to use something like LLJS is to avoid automatic memory management, but someone could certainly implement a Boehm GC however it can get quite complicated since...

We can definitely add support for bit fields, it wouldn't be that hard. But supporting back references like you mentioned is not possible, ... the size/layout of the struct needs...

I just tried it on my Mac, I get 60ms (34-88) with LLJS, 100ms (56-144) with JS in Firefox 19 Nightly. Also, the strange thing is Chrome Canary where LLJS...

Cool. I just tried it on Chrome and strangely enough the emscripten version is really slow. Benchmarking is indeed really hard.

I hear ya, but it seems to be the only way to parse without having to require type declarations. This is a problem with C style casting syntax. We actually...

Yah, it seems to be broken. I'll take a look at it.

It should be safe to use it as long as you are careful not to overwrite the header malloc generates before each allocated region.

This is a bit tricky, and what you really need is a macro pre-processor, which we don't have. `SIZE` here is an identifier and is not substituted with `100`. Imagine...

Gulp (really a simple/basic re-implementation of the Gulp API in the browser) files are running client side. The server just invokes clang with sanitized input.

> Since it is just a single HTML file, and you wouldn't need to wrangle an HTML file and a JS file and a wasm file and ... and keep...