Implement Iterator#keepLast() to allow storing last iterator value

[lundibundi]

• code is properly formatted (npm run fmt)
• tests are added/updated
• documentation is updated (npm run doc to regenerate documentation based on comments)
• description of changes is added under the Unreleased header in CHANGELOG.md

[lundibundi]

Suggested change

	get last() {
	last() {

[nechaido]

I do not like the proposed functionality as it propagates a programmer to save the iterator before the transformation. Leading to a situation where you have multiple iterators sharing a common state.

I would prefer to have a splitOn function, that will split iterator into two.

iter([1, 2, 3, 4, 5]).splitOn(v => v >= 3); // [iter([1, 2]), iter([3, 4, 5])]

[nechaido]

I don't really like lastElement sound like instead of { value: T, done: boolean } it is T.

[lundibundi]

I think the proposed splitOn is something like #339.

Will think about a better solution.

Leading to a situation where you have multiple iterators sharing a common state.

Though, what's wrong with this? I think it's already possible if someone wants to take values from the same iterator in multiple places (which is fine IMO) or misuses iterator (like using async function in .map etc).

[nechaido]

Though, what's wrong with this? I think it's already possible if someone wants to take values from the same iterator in multiple places (which is fine IMO) or misuses iterator (like using async function in .map etc).

The problem is that it forces programmers to save iterator pre-transformation.
I know that it is currently possible to misuse iterators, but I believe that we should not encourage such patterns.