-
Notifications
You must be signed in to change notification settings - Fork 178
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
Three-way comparison function for strings #364
Comments
Quoting the
On most modern processors the native character ordering will be ASCII, so the two will be de facto the same, but this is not mandated the standard. Hence, the need to maintain two sets of character comparison functions for consistency with the standard. |
The new functions you propose sound like they could be useful in some circumstances, even if they offer the same functionality. For example they can be used in a
This can be weighed against the following
|
I wonder if Fortran would allow us to use An implementation would be most suitable in |
Do you have some reason to prefer the operator syntax? Personally, I find the functional version easier to grasp and also has less characters when importing. But I'm fine with having both.
I assume these functions would follow the ASCII ordering and not the default processor one? |
I would vote for the functional version, it would be easier to get used to it. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Perl uses I would also note that the On the other side, Python 3.x decided to remove |
I went through the stdlib_string_type module and I want to recommend some changes. Correct me if I am wrong at any point.
The text was updated successfully, but these errors were encountered: