In 0.6 findfirst(::Function, ::A) would return the index of the first element that caused the predicate function to return true, and 0 if it is not present. Now it returns ‘nothing’… of type ‘Nothing’, so will this cause issue with type inference and compilation of efficient code, if you don’t know …

New findfirst behaviour - type unstable or no?

Keno Split this topic March 1, 2018, 11:11pm 4

Topic		Replies	Views
Suggestion for more general/performant sentinel for find* functions Internals & Design	17	1624	January 29, 2018
Findfirst() with Dict for which nothing is a valid key Internals & Design	2	843	February 18, 2018
New find* methods and type stability General Usage	6	1066	February 1, 2018
The new output of findfirst is dangerous General Usage	21	4123	February 24, 2018
Findfirst for Dicts with `nothing` keys General Usage	33	3336	March 4, 2018