-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
make replace
with count=0 a no-op
#22325
Merged
+45
−7
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7688517
replace with count=0 is a no-op
rfourquet 5b99e0a
document the behavior for negative count
rfourquet 2f26043
remove default in the docstring
rfourquet d387b31
use typemax(Int) instead of -1 for unlimited (nalimilan)
rfourquet bd0079a
deprecate when count < 0 and add NEWS.md entry
rfourquet 5d03ce1
avoid error when a number bigger than typemax(Int) is passed as count…
rfourquet 06a8cfd
add another commented method to be uncommented when replace removed f…
rfourquet 06a7706
check replace is implemented for GenericString (nalimilan)
rfourquet d77b51a
remove un-needed Base. prefix
rfourquet 4f60ef7
add missing backtick (nalimilan)
rfourquet 981e8da
remove unecessary `Base.` (tkelman) and cancel conversion to Int (nal…
rfourquet 4405d63
improve TODO notes (StefanKarpinski)
rfourquet ff0b955
cross-ref search (tkelman)
rfourquet 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
add another commented method to be uncommented when replace removed f…
…rom deprecated
- Loading branch information
commit 06a8cfd31f122c80f4cf9c2abd1c345dc1174ae3
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
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.
The problem with this kind of comment is that nobody is going to notice it when removing deprecation. I'd say let's go with
::Integer
, and once the deprecation has been removed, feel free to open a PR to do this.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 hasn't been addressed.
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.
Oh that's the second time since yesterday that my comment is not sent, with a "You can't perform this action at this time" message. My last unsent message was:
IOW, the comments cannot be silently ignored and it would be wrong to ignore it even if there was not this conversion-to-
Int
change (and I can open the subsequent PR in advance for the next release), but I can update if you still prefer that I postpone this one.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.
Honestly I'd rather leave this out, but let's hear what others think about it.
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.
Ok I left it out.
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 would put a TODO note in
base/deprecated.jl
referring to this and saying that it should be removed. That way there's a trail of breadcrumbs when doing the normal deprecations deletion.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.
There was already instructions in "base/deprecated.jl", but I updated to be even more clear.