Rework operator interfaces #1178
Merged
Conversation
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
Rename interfaces for arithmetic following current thinking in #1058.
zygoloid
changed the title
chandlerc
requested changes
Apr 16, 2022
| // Widgets are normally ordered by size. | ||
| external impl as Ordered { | ||
| fn Compare[me: Self](other: Self) -> Ordering { | ||
| return me.Size().(Ordered.Compare)(other.Size()); |
There was a problem hiding this comment.
(not blocking, just a side comment)
FWIW, this makes me more interested in <=> as an operator... I worry this code will be quite common.
chandlerc
requested changes
Apr 16, 2022
Co-authored-by: Chandler Carruth <chandlerc@gmail.com>
jonmeow
reviewed
Apr 22, 2022
github-actions
bot
added
the
proposal rfc
github-actions
bot
added
proposal accepted
chandlerc
added a commit
that referenced
this pull request
Jun 28, 2022
This was referenced Aug 11, 2022
chandlerc
added
the
documentation
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 3, 2023
Continued from part 1: #3231. Second step updating `docs/design/generics/details.md`. There remains some work to incorporate proposal #2200. - The biggest changes are incorporating much of the text of proposals: - #2173 - #2687 - It incorporates changes from proposals: - #989 - #1178 - #2138 - #2200 - #2360 - #2964 - #3162 - It also updates the text to reflect the latest thinking from leads issues: - #996 - #2153 -- most notably deleting the section on `TypeId`. - Update to rule for prioritization blocks with mixed type structures from [discussion on 2023-07-18](https://docs.google.com/document/d/1gnJBTfY81fZYvI_QXjwKk1uQHYBNHGqRLI2BS_cYYNQ/edit?resourcekey=0-ql1Q1WvTcDvhycf8LbA9DQ#heading=h.7jxges9ojgy3) - Adds reference links to proposals, issues, and discussions relevant to the text. - Also tries to use more precise language when talking about implementations, to avoid confusing `impl` declaration and definitions with the `impls` operator used in `where` clauses, an issue brought up in - #2495 - #2483 --------- Co-authored-by: Richard Smith <richard@metafoo.co.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add concrete design for interfaces for comparison.
Rename interfaces for arithmetic following current thinking in #1058.
Update rules for mixed-type comparisons for data classes following #710.