New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TODO] set inconsistencies #7556
Comments
I can agree only with point 3 on |
Number 4 was resolved a day ago by #7558. That leaves first two points to consider/solve. |
/cc @narimiran
Well assuming actually i don't even know why we need |
@timotheecour you could make it a pr that uses the deprecated pragma, I would vote for it. |
The deprecated pragma doesn't work for procs.
|
The length of a set is essentially one or more |
Not an inconsistency between sets and HashSets, but while we're talking about what should be implemented: The thing missing from both versions is |
Well I disagre on |
I think the rest is fine, at one point you have to stop whining and read some documentation. |
#11885 fixed item 3 in top post |
remaining item in this list would be fixed by merging #16276 and removing the (now deprecated) std/sets.toSet. |
['a', 'b'].toSet
returns aHashSet[char]
, not aset[char]
['a', 'b'].toHashSet
is not definedcard
is defined for both set and HashSet, butlen
is defined for HashSet only, not setecho({'a', 'b', 'c', 'b'}.card) : 4
(that one is already reported here:set bug: echo({'a', 'b', 'c', 'b'}.card) : 4 #7555)The text was updated successfully, but these errors were encountered: