[SR-888] Sequence.minElement() and maxElement() should be protocol requirements (customization points) · swiftlang/swift#43500

(5 comments) (0 reactions) (0 assignees)Swift (69,989 stars) (10,719 forks)batch import

affects ABIgood first issuestandard libraryswift evolution proposal needed

説明


Previous ID	SR-888
Radar	rdar://problem/24999603
Original Reporter	@gribozavr
Type	Bug
Status	In Progress
Resolution


Votes	0
Component/s	Standard Library
Labels	Bug, AffectsABI, StarterBug, StarterProposal, swift-evolution-proposal-needed
Assignee	akhilmantha (JIRA)
Priority	Medium

md5: 38f233c0b4c0d1508b74875d0c159d05

Issue Description:

Some collections naturally maintain sorted order and can implement `minElement()` and `maxElement()` in O(1). Thus, these algorithms should be protocol requirements to allow collection-specific customizations.

Note that `minElement()` and `maxElement()` that take predicates should continue to be pure extensions.

コントリビューターガイド

技術スタック: swift
領域: api
Issue 種別: feature
難度: 3
推定時間: 1-2 days
活動状況: stale
明確さ: clear
前提条件: Swift basicsProtocol oriented programming
初心者向け度: 70
調査方針: Investigate the current implementation of Sequence protocol in the Swift standard library, focusing on minElement() and maxElement() methods. Consider how to add protocol requirements for these methods to allow customization while maintaining backward compatibility. Look at existing swift evolution proposals for similar changes and check the swift dev mailing list for prior discussions.