deno_core
deno_core copied to clipboard
denoland
The core engine at the heart of Deno
This file is duplicated in `checkin`. Let's bite the bullet and add `transpile` Cargo feature that provides this loader in `core/modules/loaders` so it can be easily reused. _Originally posted by...
Life the least amount of code possible from https://github.com/denoland/deno/tree/main/cli/tools/repl and provide a simple REPL example that can be used to test out code.
At this point we have 3 distinct types of modules that are executed in `deno_core`: - `internal` modules - these are `ext:core/mod.js` and `ext:core/ops` - these modules are provided automatically...
Currently all registered ops are "added" as JavaScript bindings twice: 1. To `Deno.core.ops` module in: https://github.com/denoland/deno_core/blob/ce620969c447d5cd7d7c21e1b95bc120c67142be/core/runtime/bindings.rs#L268-L298 2. To `ext:core/ops` synthetic module in: https://github.com/denoland/deno_core/blob/ce620969c447d5cd7d7c21e1b95bc120c67142be/core/runtime/bindings.rs#L773-L796 We actually need both approaches - the...
The second test, which uses `destructureError` (underlying op being `op_destructure_error`), adds a frame for unknown reasons. Additionally, for some reason, `AggregregateError`s don't have any stack frames.
`exception_to_err_result` grew organically over the years and has become really untenable. It has two floating boolean arguments, that control important side effect and IMO it's very easy to misuse. The...
To prevent problems like https://github.com/denoland/deno_core/pull/405, we should add some minimal integration tests for our examples/ directory that would assert specific output. We should use the same approach we use in...
``` #[op2(fast)] pub fn op_v8slice_store_32( #[state] test_data: &mut TestData, #[string] name: String, #[buffer] data: V8Slice, ) { test_data.insert(name, data); } ``` ``` mismatched types expected struct `V8Slice` found struct `deno_core::v8::Local
