-
-
Notifications
You must be signed in to change notification settings - Fork 411
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
Add a Source::with_path method to set the path on a Source #3941
Merged
Merged
Changes from 2 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
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.
nit: doc might be a bit unclear wording wise. As it's not adding the path to the current
Source
, but is creating a newSource
from the combination.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.
It takes ownership of the source, so it's used like any
with_
method. I can use the same wording asJsError::with_message
;Sets the path of this Source
.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.
Ah, I've been dealing with different
with_
methods recently with temporal 😆 I guess I'm a bit curious about takingself
vs.mut self
in this instance.Basically, if I'm reading this correctly, this method could probably be:
I think the above tends to be more in line with convention, and we also aren't potentially dropping the previous
self
, granted maybe rustc optimizes that out and it doesn't matter that much.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.
@nekevss Uhh I think your method doesn't work in general because it doesn't change the lifetime of
Source
to be the same as the lifetime ofPath
. It would (probably) work with lifetimes that are sub-lifetimes of'path
, but we don't want to add that arbitrary restriction.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.
True. I think I'm getting caught up on a bit of a bikeshed around the name/behavior of this method.
😕 if we are destroying
Source
anyways, then wouldn't it be a bit clearer convention wise for the method to be ato_
(something liketo_source_with_path
)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 think using
with_*
methods that takeself
is pretty common e.g. builder types. I don't see a problem with using the same convention for this.