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
[stdlib] String comparisons implemented #2409
Closed
+188
−0
Closed
Changes from 7 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
ccbe327
[stdlib] Implemented __lt__, __le__, __gt__, & __ge__ for String, and…
siitron 3a0146b
[stdlib] Whitespace and formatting fix.
siitron d84deef
[stdlib] Removed an accidental variable redefiniton in test_compariso…
siitron 69c1d12
[stdlib] small change to String's test_comparison_operators()
siitron c9d58da
[stdlib] Implemented __lt__, __le__, __gt__, & __ge__ for StringLiter…
siitron 9dea5b9
Merge branch 'modularml:nightly' into nightly
siitron 3439ea3
[stdlib] Replaced invalid usages of math.min in string.mojo and strin…
siitron 3295806
Merge branch 'modularml:nightly' into nightly
siitron 47701d8
Merge branch 'modularml:nightly' into nightly
siitron b17a855
Merge branch 'modularml:nightly' into nightly
siitron 13cb73b
Merge branch 'modularml:nightly' into nightly
siitron 2b73124
Merge branch 'modularml:nightly' into nightly
siitron 5b03ae8
[stdlib] Replaced ._as_ptr() with .unsafe_ptr() in String and StringL…
siitron File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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
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.
Suggestion: you can consolidate the duplication between this and the implementation in String by implementing the comparison on StringRef
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.
Do you mean something like
return StringRef(self) < StringRef(rhs)
as__lt__
for StringLiteral (andreturn self._strref_dangerous() < rhs._strref_dangerous()
for String), etc.?I didn't even consider StringRef (forgot it existed), and I tried to match
__lt__
with their respective__eq__
-methods. Right now String, StringLiteral, and StringRef does__eq__
in three separate ways, so I thought there was some reason for keeping them apart ATM(?). Would it still be safe to usememory.memcmp
in the StringRef__lt__
implementation (considering it currently looks like StringLiteral has to use it's own local_memcmp
, and StringRef's__eq__
also avoids it), or should StringRef's__lt__
be done like its__eq__
?What do you think of: