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

(5 评论) (0 反应) (0 负责人)Swift (69,989 star) (10,719 fork)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
议题类型: 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.