Well, it does have the slight problem: d=Dict(); d[1]=1; d[nothing]=2; d #Dict{Any,Any} with 2 entries: # nothing => 2 # 1 => 1 @show findfirst(equalto(0), d) #findfirst(equalto(0), d) = nothing @show findfirst(equalto(1), d) #findfirst(equalto(1), d) = 1 @show findfirst(equalto(2), d) #f…

[image] The new output of findfirst is dangerous There can be no confusion as to whether a match was found or not That’s not true, if nothing can be an index (key) into the collection. All the change did was hurt performance and move the place where things break down from one place (where 0 m…

Findfirst() with Dict for which nothing is a valid key

Internals & Design

nalimilan February 18, 2018, 11:17am 3

Topic		Replies	Views
Findfirst for Dicts with `nothing` keys General Usage	33	3656	March 4, 2018
How to distinguish between "found" and "not found" in `findfirst(dict)`? E.g.:``` General Usage	1	291	February 25, 2021
Suggestion for more general/performant sentinel for find* functions Internals & Design	17	1731	January 29, 2018
The new output of findfirst is dangerous General Usage	21	4373	February 24, 2018
New findfirst behaviour - type unstable or no? General Usage	5	1235	March 1, 2018

Findfirst() with Dict for which nothing is a valid key

Related topics