8fe9b8a4cc
Implements `Result` in fast-calls. Note that the approach here is slightly different. Rather than store the last result in the `OpState`, we put it into the `OpCtx` which saves us a lookup and lock in the error case. We do not have to lock this field as it's guaranteed only one runtime and thread can ever access it. The fastcall path for many ops can avoid doing a great deal of work, even for `Result` return values. In the previous iteration of `ops`, all `Result`-returning functions would fetch and lock the `OpState`, regardless of whether it was used or not. |
||
|---|---|---|
| .. | ||
| examples | ||
| modules | ||
| runtime | ||
| 00_primordials.js | ||
| 01_core.js | ||
| 02_error.js | ||
| async_cancel.rs | ||
| async_cell.rs | ||
| Cargo.toml | ||
| error.rs | ||
| error_codes.rs | ||
| extensions.rs | ||
| fast_string.rs | ||
| flags.rs | ||
| gotham_state.rs | ||
| inspector.rs | ||
| internal.d.ts | ||
| io.rs | ||
| lib.deno_core.d.ts | ||
| lib.rs | ||
| module_specifier.rs | ||
| normalize_path.rs | ||
| ops.rs | ||
| ops_builtin.rs | ||
| ops_builtin_v8.rs | ||
| ops_metrics.rs | ||
| path.rs | ||
| README.md | ||
| resources.rs | ||
| source_map.rs | ||
| task.rs | ||
| task_queue.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/main.rs as examples of usage.
TypeScript support and lots of other functionality are not available at this layer. See the CLI for that.