[documentation]: document the splitwhile tactic

[strub]

No description provided.

[fdupress]

I know we're still quite fragmented, but I think @Cameron-Low had pretty good documentation for intro-patterns and (more importantly in this context) code positions over in the ec-tactic repo.

Is it worth linking to that when talking about code positions? (Not ideal for the user.)
Or wait until we carry it over and add all links at that point? (That sounds like an excellent reason to never document code positions, which is bad.)

[strub]

I know we're still quite fragmented, but I think @Cameron-Low had pretty good documentation for intro-patterns and (more importantly in this context) code positions over in the ec-tactic repo.

Is it worth linking to that when talking about code positions? (Not ideal for the user.) Or wait until we carry it over and add all links at that point? (That sounds like an excellent reason to never document code positions, which is bad.)

Yes, this is a question I asked to myself. We clearly want to link back to the relevant chapters/sections. Maybe should we draft a TOC so that we can start linking to them. Better to do it on the fly than to do it at the end.