Deno for the runtime

[jeromegn]

This project is heavily inspired by deno and in a lot of cases uses code from deno directly.

Talking with Ryan Dahl, we've determined deno should be embeddable in other rust projects. It would be nice to use deno directly since it's improving rapidly (performance, security, features) and bringing all its changes is hard.

There are some things we're "waiting" for before we can make the switch:

• [ ] Deno as a rust crate (https://github.com/denoland/deno/issues/695)
• [ ] Memory limits (both max-old-space and allocations)
  • [ ] Inspecting the memory usage (V8's GetHeapStatistics + allocated space)
• [ ] Uncaught exception and promise rejection callbacks (ability to only crash the runtime and not the whole process)
• [ ] Custom operation handlers (including flatbuffers message)
  • [ ] Opt-in / opt-out for built-in operations
• [ ] Custom snapshots
• [ ] print callback with log "level" to handle logs differently

[ry]

Cool - thanks for the reference. We've just about got "cargo check" working - and after that it's a quick hop to "cargo build" and publishing a crate. I expect to have a crate published next week.

Once you can import the deno crate easily, we'll discuss the rest.

(I'm very interested in exposing memory stats. We need to track allocs for our internal tests too. I think we can model it after https://golang.org/pkg/runtime/#MemStats)

check out the WIP generated rust docs: http://deno.land/doc/deno/isolate/struct.Isolate.html