Add List.find

[rtfeldman]

This adds List.find, a useful function I've been using in a personal Util.elm file, but which seems like a good candidate for inclusion in core given that it's standard in several languages, for example:

• JavaScript
• Ruby
• Scala
• Haskell

[texastoland]

This should proxy to Native right? I've been wondering whether there's criteria for Core inclusion.

[texastoland]

This should proxy to Native right? I've been wondering whether there's criteria for Core inclusion.

[rtfeldman]

Would proxying to Native improve this though? With the impending self-TCO this compiles to a while loop anyway, yeah?

[rtfeldman]

Would proxying to Native improve this though? With the impending self-TCO this compiles to a while loop anyway, yeah?

[texastoland]

Native JS uses C++ cheats. Based on O(1) optimizations V8 performs on property access it's reasonable to imagine find() using a reverse cache lookup on object ID. In general if there's a native function we should always proxy.

[texastoland]

Native JS uses C++ cheats. Based on O(1) optimizations V8 performs on property access it's reasonable to imagine find() using a reverse cache lookup on object ID. In general if there's a native function we should always proxy.

[texastoland]

PS I agree it should be included I just wish we had a criteria for completeness and rejection.

[texastoland]

PS I agree it should be included I just wish we had a criteria for completeness and rejection.

[evancz]

For now the recommended way of extending the standard libraries is in a package, like elm-list-extra or elm-random-extra. There can be lots of experimentation with APIs there that does not block on me or the release cycle of elm-lang/core. At some point, we will go through and try to merge in all the best things about the *-extra world in a coherent way.

I suspect @rehno-lindeque would accept this function in elm-list-extra, try a PR there for now.

[evancz]

For now the recommended way of extending the standard libraries is in a package, like elm-list-extra or elm-random-extra. There can be lots of experimentation with APIs there that does not block on me or the release cycle of elm-lang/core. At some point, we will go through and try to merge in all the best things about the *-extra world in a coherent way.

I suspect @rehno-lindeque would accept this function in elm-list-extra, try a PR there for now.

[texastoland]

Thanks for the clarification @evancz makes sense to me 👍

[texastoland]

Thanks for the clarification @evancz makes sense to me 👍

[rtfeldman]

Fair enough! Moved the PR to elm-list-extra.

[rtfeldman]

Fair enough! Moved the PR to elm-list-extra.