Skip to content

Conversation

awwright
Copy link

@awwright awwright commented Oct 2, 2025

No description provided.

@awwright
Copy link
Author

awwright commented Oct 2, 2025

This proposal seems to have fallen into an exceptional state where it's "accepted" but not being implemented. This has caused much confusion, e.g.

https://forums.swift.org/t/accepted-se-0283-tuples-conform-to-equatable-comparable-and-hashable/36658/10
https://forums.swift.org/t/status-of-se-0283-tuples-conform-to-equatable-comparable-and-hashable/46942
https://forums.swift.org/t/why-isnt-my-int-int-hashable/82400

I'm not able to find any process that describes what to do in this situation, but it probably shouldn't be sitting around as "Accepted"

@xwu
Copy link
Contributor

xwu commented Oct 3, 2025

I believe the status we assign to such proposals is "expired"—because these fields are parsed by various tooling, they're not really freeform anymore and it's possible we've been labeling them "rejected." In any case, an announcement on the status change is due as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants