You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For historical reasons, HPACKHeaders does not pay attention to order or indexability when considering equality and hashability. We should consider whether this is appropriate for this type, or whether we should make the definition more strict.
The text was updated successfully, but these errors were encountered:
Motivation:
HPACKHeaders is equatable, and it rarely makes sense to have a type that
is equatable but not hashable. The definition of equatability is pretty
limited here (see apple#342) but we can define a definition of hashability
consistent with it.
Modifications:
- Make HPACKHeaders hashable.
Result:
People can store HPACKHeaders in Sets
I don't think that's really the right thing to do. We should commit the core type to one of those two positions, and where necessary we can always expose the other.
Motivation:
HPACKHeaders is equatable, and it rarely makes sense to have a type that
is equatable but not hashable. The definition of equatability is pretty
limited here (see #342) but we can define a definition of hashability
consistent with it.
Modifications:
- Make HPACKHeaders hashable.
Result:
People can store HPACKHeaders in Sets
Co-authored-by: David Nadoba <dnadoba@gmail.com>
For historical reasons, HPACKHeaders does not pay attention to order or indexability when considering equality and hashability. We should consider whether this is appropriate for this type, or whether we should make the definition more strict.
The text was updated successfully, but these errors were encountered: