e2a0c3f0dc
This commit completely rewrites inspector session polling. Until now, there was a single function responsible for polling inspector sessions which could have been called when polling the "JsRuntime" as well as from internal inspector functions. There are some cases where it's required to have reentrant polling of sessions (eg. when "debugger" statement is run) which should be blocking until inspector sends appropriate message to continue execution. This was not possible before, because polling of sessions didn't have reentry ability. As a consequence, session polling was split into two separate functions: a) one to be used when polling from async context (on each tick of event loop in "JsRuntime") b) one to be used when polling synchronously and potentially blocking (used by various inspector methods). There are further cleanups and simplifications to be made in inspector code, but this rewrite solves the problem at hand (being able to evaluate "debugger" JS statement and continue inspector functionality). Co-authored-by: Bert Belder <bertbelder@gmail.com> |
||
---|---|---|
.. | ||
examples | ||
00_primordials.js | ||
01_core.js | ||
02_error.js | ||
async_cancel.rs | ||
async_cell.rs | ||
bindings.rs | ||
Cargo.toml | ||
encode_decode_test.js | ||
error.rs | ||
error_builder_test.js | ||
error_codes.rs | ||
extensions.rs | ||
flags.rs | ||
gotham_state.rs | ||
icudtl.dat | ||
inspector.rs | ||
internal.d.ts | ||
io.rs | ||
lib.deno_core.d.ts | ||
lib.rs | ||
module_specifier.rs | ||
modules.rs | ||
normalize_path.rs | ||
ops.rs | ||
ops_builtin.rs | ||
ops_builtin_v8.rs | ||
ops_metrics.rs | ||
README.md | ||
resources.rs | ||
runtime.rs | ||
serialize_deserialize_test.js | ||
snapshot_util.rs | ||
source_map.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).
Rust functions can be registered in JavaScript using deno_core::Extension
. Use
the Deno.core.ops.op_name()
and Deno.core.opAsync("op_name", ...)
functions
to trigger the op function callback. A conventional way to write ops is using
the deno_ops
crate.
Documentation for this crate is thin at the moment. Please see hello_world.rs and http_bench_json_ops.rs as examples of usage.
TypeScript support and lots of other functionality are not available at this layer. See the CLI for that.