-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: mark op1 as deprecated and port most core ops #279
Conversation
1fe9416
to
ec22190
Compare
ec22190
to
7333af6
Compare
|
||
// This is a hack to make the `#[op]` macro work with | ||
// deno_core examples. | ||
// You can remove this: | ||
use deno_core::*; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a more convenient import for most of the examples, so leaving it here (it's no longer required though)
use deno_core::OpState; | ||
use deno_core::Resource; | ||
use deno_core::ResourceId; | ||
use deno_core::*; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
@@ -288,42 +289,6 @@ fn test_op_detached_buffer() { | |||
.unwrap(); | |||
} | |||
|
|||
#[test] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unused feature, just removing for now
@@ -1,4 +1,5 @@ | |||
// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license. | |||
use crate as deno_core; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might remove the op2(core)
and just do this in the rare files in deno_core that have ops. core
adds quite a bit of noise to the internal ops and it really isn't required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll follow up with it in a later pass!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can remove this file altogether I think. It's named http_bench_json_ops
- it has nothing to do with JSON ops that we did in 2020 or 2021 :D
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance).
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance).
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance).
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance). The deno runtime version now comes directly from the deno snapshot. For our usage, that means that the `Deno.version.deno` and `Deno.version.v8` values are now empty strings where they were previously the Phylum version and v8 version respectively.
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance). The deno runtime version now comes directly from the deno snapshot. For our usage, that means that the `Deno.version.deno` and `Deno.version.v8` values are now empty strings where they were previously the Phylum version and v8 version respectively.
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance). The deno runtime version now comes directly from the deno snapshot. For our usage, that means that the `Deno.version.deno` and `Deno.version.v8` values are now empty strings where they were previously the Phylum version and v8 version respectively.
This includes migration to the new `op2` macro because `op` is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance). The deno runtime version now comes directly from the deno snapshot. For our usage, that means that the `Deno.version.deno` and `Deno.version.v8` values are now empty strings where they were previously the Phylum version and v8 version respectively.
Before we remove
#[op]
, give embedders some notice to switch over to#[op2]
. Note that I could not port the wasm ops yet -- we'll address that in #275