mirror of
https://github.com/denoland/deno.git
synced 2024-11-22 15:06:54 -05:00
a569be861a
* migrate deno_typescript crate to Isolate.register_op API * remove dual-dispatch mechanism * update Isolate tests to new dispatch mechanism |
||
|---|---|---|
| .. | ||
| examples | ||
| libdeno | ||
| any_error.rs | ||
| build.rs | ||
| Cargo.toml | ||
| flags.rs | ||
| isolate.rs | ||
| js_errors.rs | ||
| lib.rs | ||
| libdeno.rs | ||
| module_specifier.rs | ||
| modules.rs | ||
| ops.rs | ||
| README.md | ||
| shared_queue.js | ||
| shared_queue.rs | ||
| shared_queue_test.js | ||
Deno Core
This Rust crate contains the essential V8 bindings for Deno's command-line
interface (Deno CLI). The main abstraction here is the Isolate which provides a
way to execute JavaScript. The Isolate is modeled as a
Future<Item=(), Error=JSError> which completes once all of its ops have
completed.
In order to bind Rust functions into JavaScript, use the Deno.core.dispatch()
function to trigger the "dispatch" callback in Rust. The user is responsible for
encoding both the request and response into a Uint8Array.
Documentation for this crate is thin at the moment. Please see http_bench.rs as a simple example of usage.
TypeScript support and a lot of other functionality is not available at this layer. See the cli for that.