foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 15:04:11 -05:00
Code Issues Packages 1 Wiki Activity

chore(core): update deno_core README (#14042)

Browse source 
Co-authored-by: Andreu Botella <andreu@andreubotella.com>
This commit is contained in:
Divy Srivastava 2022-03-20 16:08:35 +05:30 committed by GitHub
parent 7c2722201e
commit 5e82bcf0e4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
core/README.md
View file

@ -16,10 +16,10 @@ 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.
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.
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)