Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add `findSliceIndex` function to other collections

See original GitHub issue

Description

I propose we add findSliceIndex / tryFindSliceIndex which we recently added to String extension to other collections’ extensions.

val findSliceIndex : slice:'Collection<'a> -> source:'Collection<'a> -> int

val tryFindSliceIndex : slice:'Collection<'a> -> source:'Collection<'a> -> int option

It will work just like ~~the existing findIndex : 'a -> 'Collection<'a> -> int but it searches a “slice” (i.e. subsequence, sub-collection) instead of an element~~ String.findIndex.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

2reactions

gustycommented, Jul 29, 2019

I’m personally fine with this, definitely it makes sense to have them for other collections.

It also makes sense to have the generic version, if you are willing to do this PR I leave it to your criteria/willingness to include the generic functions or not.

Of course, I’m happy to help fighting the compiler 😉

1reaction

gustycommented, Jul 30, 2019

Yes, go ahead please !