summaryrefslogtreecommitdiff
path: root/core/README.md
diff options
context:
space:
mode:
authorRyan Dahl <ry@tinyclouds.org>2020-10-10 05:41:11 -0400
committerGitHub <noreply@github.com>2020-10-10 11:41:11 +0200
commit08bb8b3d53eb2445de9b5e2845ab8acf9d353800 (patch)
treeebf00cb815ee1a10be00c74cbb332af33dd52dc2 /core/README.md
parent782e6a2ed5d76bb5a154c56d7daf4607e5bdb93f (diff)
Fix 100% CPU idling problem by reverting #7672 (#7911)
* Revert "refactor: Worker is not a Future (#7895)" This reverts commit f4357f0ff9d39411f22504fcc20db6bd5dec6ddb. * Revert "refactor(core): JsRuntime is not a Future (#7855)" This reverts commit d8879feb8c832dbb38649551b1cb0730874f7be6. * Revert "fix(core): module execution with top level await (#7672)" This reverts commit c7c767782538243ded64742dca9b34d6af74d62d.
Diffstat (limited to 'core/README.md')
-rw-r--r--core/README.md9
1 files changed, 3 insertions, 6 deletions
diff --git a/core/README.md b/core/README.md
index 2438ecede..f6b429bb8 100644
--- a/core/README.md
+++ b/core/README.md
@@ -9,12 +9,9 @@ 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).
+a way to execute JavaScript. The JsRuntime is modeled as a
+`Future<Item=(), Error=JsError>` which completes once all of its ops have
+completed.
In order to bind Rust functions into JavaScript, use the `Deno.core.dispatch()`
function to trigger the "dispatch" callback in Rust. The user is responsible for