# SE-0203 — Rename Sequence.elementsEqual **URL:** \ **Category:** Proposal Reviews\ **Created:** [March 29, 2018, 4:31pm UTC](https://forums.swift.org/t/se-0203-rename-sequence-elementsequal/11482 "2018-03-29T16:31:35Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![palimondo](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/palimondo/32/1144_2.png) [@palimondo](https://forums.swift.org/u/palimondo)\ **Post date:** [April 1, 2018, 5:32pm UTC](https://forums.swift.org/t/se-0203-rename-sequence-elementsequal/11482/24 "2018-04-01T17:32:32Z")
Method name `elementsEqual` looks reasonable on `Sequence` but gets outright misleading, when used on concrete types. The problem is lessened post Swift 4.1 by conditional conformances for `Set`s of `Equatable` elements that gives you `==`. But to me, the proposed five word method name represents the worst of excessively literal Cocoa naming, which doesn’t feel Swifty at all. **`sequentiallyEqual`** proposed up-thread is much better. That name was even proposed in [4th reply to the original discussion thread](https://forums.swift.org/t/draft-rename-sequence-elementsequal/6821/4). My search there hasn’t revealed any valid counter argument against that name other than preoccupation with `lexicographicallyEqual`, which isn’t part of the updated proposal we vote on… --- _[View the full topic](https://forums.swift.org/t/se-0203-rename-sequence-elementsequal/11482)._