46c0cab763
This commit rewrites initialisation of the "shared queue" and in effect prevents from double execution of "core/core.js" and "core/error.js". Previously both of these files were executed every time a "JsRuntime" was created. That lead to a situation where one copy of each script was included in the snapshot and then another copy would be executed after loading the snapshot. Effectively "JsRuntime::shared_init" was removed; instead execution of those scripts and actual initialisation of shared queue was split into two helper functions: "JsRuntime::js_init" and "JsRuntime::share_queue_init". Additionally stale TODO comments were removed. |
||
---|---|---|
.. | ||
examples | ||
async_cancel.rs | ||
async_cell.rs | ||
bindings.rs | ||
Cargo.toml | ||
core.js | ||
core_test.js | ||
encode_decode_test.js | ||
error.js | ||
error.rs | ||
flags.rs | ||
gotham_state.rs | ||
lib.rs | ||
module_specifier.rs | ||
modules.rs | ||
normalize_path.rs | ||
ops.rs | ||
plugin_api.rs | ||
README.md | ||
resources.rs | ||
runtime.rs | ||
shared_queue.rs | ||
zero_copy_buf.rs |
Deno Core Crate
The main dependency of this crate is rusty_v8, which provides the V8-Rust bindings.
This Rust crate contains the essential V8 bindings for Deno's command-line interface (Deno CLI). The main abstraction here is the JsRuntime which provides a way to execute JavaScript.
The JsRuntime implements an event loop abstraction for the executed code that
keeps track of all pending tasks (async ops, dynamic module loads). It is user's
responsibility to drive that loop by using JsRuntime::run_event_loop
method -
it must be executed in the context of Rust's future executor (eg. tokio, smol).
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_bin_ops.rs and http_bench_json_ops.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.