Any reason struct SIMD is missing the EqualityComparable trait? It appears to have the methods implemented. As shown below, I’m seeing the error: argument type 'SIMD[uint64, 1]' does not conform to trait 'EqualityComparable & Copyable & Movable' Mojo 25.4.0.dev2025060805 foos = List[UInt64]() som…

EqualityComparable means returning single boolean. But comparison with vector means returning vector of boolean. [1, 2, 3, 4] == [1, 2, 5, 6] # [True,True,False,False] So you can’t return single boolean for vector. As for scalar case It will be added after the requires clause is added.

Using DType.uint64 as shown below emits an error on assignment, cannot implicitly convert 'DType' value to 'Copyable & Movable' in type parameter. fn main(): # cannot implicitly convert 'DType' value to 'Copyable & Movable' in type parameter foos = List[DType.uint64]() # <-- Error here …

Yep, my 2c is that we need to fix this. SIMD not conforming to equatable and comparable will break pretty much all generic algorithms from working with floating point and sized integer types, and will prevent merging Int and UInt into SIMD someday.

Agreed. This is one of the team’s priorities for Q3.

Struct SIMD - Missing trait 'EqualityComparable'?

Mojo

xtxtxtxtxtx (xtx) June 8, 2025, 11:53pm 4

Also there is a thread below too.Why Float is Not Comparable

Topic		Replies	Views
Why is float not comparable Standard Library	9	274	June 4, 2025
List of struct error Mojo	3	105	May 28, 2025
Cannot pass 'DType' value, expected 'AnyTrivialRegType' in call parameter Mojo	2	103	October 18, 2025
How can we compare parameterized types ignoring parameter types? Mojo	4	164	October 18, 2025
Interval not implementing 'Comparable' trait Mojo discussion	4	184	December 20, 2025

Struct SIMD - Missing trait 'EqualityComparable'?

Related topics