0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-10-29 08:58:01 -04:00
denoland-deno/core
Luca Casonato 53088e16de
feat(test): improved op sanitizer errors + traces (#13676)
This commit improves the error messages for the `deno test` async op
sanitizer. It does this in two ways:
- it uses handwritten error messages for each op that could be leaking
- it includes traces showing where each op was started

This "async op tracing" functionality is a new feature in deno_core.
It likely has a significant performance impact, which is why it is only
enabled in tests.
2022-02-16 19:53:17 +01:00
..
examples example(core): Add example for TypeScript transpiling via deno_ast (#13545) 2022-01-31 13:43:32 +01:00
00_primordials.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
01_core.js feat(test): improved op sanitizer errors + traces (#13676) 2022-02-16 19:53:17 +01:00
02_error.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
async_cancel.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
async_cell.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
bindings.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
Cargo.toml chore: update v8 (#13680) 2022-02-16 13:14:34 +01:00
encode_decode_test.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
error.rs chore: upgrade to rust 1.58 (#13377) 2022-01-15 07:10:12 +01:00
error_builder_test.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
error_codes.rs refactor: re-export anyhow from deno_core (#12777) 2021-11-16 09:02:28 -05:00
extensions.rs refactor: re-export anyhow from deno_core (#12777) 2021-11-16 09:02:28 -05:00
flags.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
gotham_state.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
icudtl.dat upgrade: rusty_v8 0.23.0 (V8 9.2.230.12) (#11113) 2021-06-25 12:54:53 +02:00
inspector.rs refactor: factor out CDP message types (#13551) 2022-02-07 17:05:49 +01:00
internal.d.ts chore: update copyright year (#13434) 2022-01-20 16:10:16 +09:00
lib.deno_core.d.ts feat(test): improved op sanitizer errors + traces (#13676) 2022-02-16 19:53:17 +01:00
lib.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
module_specifier.rs chore: upgrade to rust 1.58 (#13377) 2022-01-15 07:10:12 +01:00
modules.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
normalize_path.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
ops.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
ops_builtin.rs refactor: re-export anyhow from deno_core (#12777) 2021-11-16 09:02:28 -05:00
ops_json.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
ops_metrics.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
README.md docs(core): replaces dispatch references with op (#11054) 2021-06-20 17:12:55 +02:00
resources.rs chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
runtime.rs refactor(core): Extract JsRuntime::poll_value out of JsRuntime::resolve_value (#13461) 2022-01-24 17:59:41 +01:00
serialize_deserialize_test.js chore: update rusty_v8 (#13575) 2022-02-02 18:51:37 +01:00

Deno Core Crate

crates docs

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.opSync() and Deno.core.opAsync() functions to trigger the "op_fn" callback in JsRuntime::register_op on Rust side. A conventional way to handle "op_fn" callbacks is to use the op_sync and op_async functions.

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.