mirror of
https://github.com/denoland/deno.git
synced 2024-11-22 15:06:54 -05:00
f356b2bd5e
After landing #3358 the benchmarks exploded indicating problems with workers and deno_core_http_bench. This PR dramatically fixes thread/syscall count that showed up on benchmarks. Thread count is not back to previous levels but difference went from hundreds/thousands to about ~50. |
||
|---|---|---|
| .. | ||
| examples | ||
| libdeno | ||
| any_error.rs | ||
| build.rs | ||
| Cargo.toml | ||
| flags.rs | ||
| isolate.rs | ||
| js_errors.rs | ||
| lib.rs | ||
| libdeno.rs | ||
| module_specifier.rs | ||
| modules.rs | ||
| ops.rs | ||
| README.md | ||
| resources.rs | ||
| shared_queue.js | ||
| shared_queue.rs | ||
| shared_queue_test.js | ||
Deno Core
This Rust crate contains the essential V8 bindings for Deno's command-line
interface (Deno CLI). The main abstraction here is the Isolate which provides a
way to execute JavaScript. The Isolate 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
encoding both the request and response into a Uint8Array.
Documentation for this crate is thin at the moment. Please see http_bench.rs as a simple example of usage.
TypeScript support and a lot of other functionality is not available at this layer. See the cli for that.