-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Remove dead code: legacy read/write ops #2776
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
use super::dispatch_minimal::MinimalOp; | ||
use crate::deno_error; | ||
use crate::resources; | ||
use crate::tokio_write; | ||
use deno::ErrBox; | ||
use deno::PinnedBuf; | ||
use futures::Future; | ||
|
||
pub fn op_read(rid: i32, zero_copy: Option<PinnedBuf>) -> Box<MinimalOp> { | ||
debug!("read rid={}", rid); | ||
let zero_copy = match zero_copy { | ||
None => { | ||
return Box::new(futures::future::err(deno_error::no_buffer_specified())) | ||
} | ||
Some(buf) => buf, | ||
}; | ||
match resources::lookup(rid as u32) { | ||
None => Box::new(futures::future::err(deno_error::bad_resource())), | ||
Some(resource) => Box::new( | ||
tokio::io::read(resource, zero_copy) | ||
.map_err(ErrBox::from) | ||
.and_then(move |(_resource, _buf, nread)| Ok(nread as i32)), | ||
), | ||
} | ||
} | ||
|
||
pub fn op_write(rid: i32, zero_copy: Option<PinnedBuf>) -> Box<MinimalOp> { | ||
debug!("write rid={}", rid); | ||
let zero_copy = match zero_copy { | ||
None => { | ||
return Box::new(futures::future::err(deno_error::no_buffer_specified())) | ||
} | ||
Some(buf) => buf, | ||
}; | ||
match resources::lookup(rid as u32) { | ||
None => Box::new(futures::future::err(deno_error::bad_resource())), | ||
Some(resource) => Box::new( | ||
tokio_write::write(resource, zero_copy) | ||
.map_err(ErrBox::from) | ||
.and_then(move |(_resource, _buf, nwritten)| Ok(nwritten as i32)), | ||
), | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm not a fan of this name. I always imagined "dispatcher" as a function which maps "op id" to "op handler".
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.
that's what this does (modulo the op id part)
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.
Mmmm, I'm not sure. It looks like
Dispatcher
is actually an "op", it returnsMinimalOp
which is the result of that op. I had a feeling that it was supposed to be thatDispatcher
selectsMinimalOp
which returns someMinimalOpResult
. But that's nomenclature... just thinking out loudThere 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.
Op = Promise = Future .. there are many ops for each dispatcher. An OpDispatcher (yet to be defined but outlined in #2730) is something that returns an Op.
So I think the term Dispatcher is appropriate here. That said, I consider this bit ephemeral as I plan on adding the OpDispatcher trait soon.