mirror of
https://github.com/denoland/deno.git
synced 2024-11-25 15:29:32 -05:00
cd61c01545
Remove `ExtensionFileSourceCode::LoadedFromFsDuringSnapshot` and feature `include_js_for_snapshotting` since they leak paths that are only applicable in this repo to embedders. Replace with feature `exclude_js_sources`. Additionally the feature `force_include_js_sources` allows negating it, if both features are set. We need both of these because features are additive and there must be a way of force including sources for snapshot creation while still having the `exclude_js_sources` feature. `force_include_js_sources` is only set for build deps, so sources are still excluded from the final binary. You can also specify `force_include_js_sources` on any extension to override the above features for that extension. Towards #19398. But there was still the snapshot-from-snapshot situation where code could be executed twice, I addressed that by making `mod_evaluate()` and scripts like `core/01_core.js` behave idempotently. This allowed unifying `ext::init_ops()` and `ext::init_ops_and_esm()` into `ext::init()`. |
||
|---|---|---|
| .. | ||
| benches | ||
| Cargo.toml | ||
| js_runtime.rs | ||
| lib.rs | ||
| profiling.rs | ||
| README.md | ||
Benching utility for deno_core op system
Example:
use deno_bench_util::bench_or_profile;
use deno_bench_util::bencher::{benchmark_group, Bencher};
use deno_bench_util::bench_js_sync};
use deno_core::op_sync;
use deno_core::serialize_op_result;
use deno_core::Extension;
use deno_core::JsRuntime;
use deno_core::Op;
use deno_core::OpState;
fn setup() -> Vec<Extension> {
let custom_ext = Extension::builder()
.ops(vec![
("op_nop", |state, _| {
Op::Sync(serialize_op_result(Ok(9), state))
}),
])
.build();
vec![
// deno_{ext}::init(...),
custom_ext,
]
}
fn bench_op_nop(b: &mut Bencher) {
bench_js_sync(b, r#"Deno.core.ops.op_nop();"#, setup);
}
benchmark_group!(benches, bench_op_nop);
bench_or_profile!(benches);