diff options
| author | Divy Srivastava <dj.srivastava23@gmail.com> | 2022-10-21 19:35:23 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-21 19:35:23 +0530 |
| commit | 0f27b84a5caa10d9056b7a4f9eace3771f8ea114 (patch) | |
| tree | 60c51b69e36f520d653185d5ce9769e5311ad111 /core/README.md | |
| parent | 659a918f39c516fe90cab25facb02325e5e72371 (diff) | |
chore(core): remove `core.opSync` (#16379)
This patch removes the last uses of `core.opSync` from Deno.
The new and JIT-friendly way to call sync ops is `core.ops.op_name()`.
Diffstat (limited to 'core/README.md')
| -rw-r--r-- | core/README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/core/README.md b/core/README.md index 08ac072cf..df0db5de3 100644 --- a/core/README.md +++ b/core/README.md @@ -17,9 +17,9 @@ 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.opSync()` and `Deno.core.opAsync()` functions to trigger the op -function callback. A conventional way to write ops is using the -[`deno_ops`](https://github.com/denoland/deno/blob/main/ops) crate. +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`](https://github.com/denoland/deno/blob/main/ops) crate. Documentation for this crate is thin at the moment. Please see [hello_world.rs](https://github.com/denoland/deno/blob/main/core/examples/hello_world.rs) |