foreachbug? That should be backported anyway, so maybe we could just cut an 0.9.1 today with that and not publish 0.10.0 with a potential stack bug?
@travisbrown Hi there
I have a question regarding
Is it called after last step processed or failed?
Let's say, I have an
Enumerator of futures, and I want to close connection on reading failure or when I'm done with stream.
Currently it seems like
.ensure is called before the last element is processed (if I add it here):
I got an exception every time when I write inside of the
https://github.com/ImLiar/finch/blob/246fd7ccf80e9da9d8fedd409fbf09ce2d7bda18/iteratee/src/test/scala/io/finch/iteratee/EnumerateEndpointSpec.scala#L45 saying that writer is already closed
Trysupported by explicitly lazy methods with the
And one more question
I have two
append one to another. Both of them have
ensureEval. What will be the behaviour in that case? Will the
ensure happen after both streams are done:
stream1 -> stream2 -> ensure1 -> ensure2
or it's gonna be like:
stream1 -> ensure1 -> stream2 -> ensure2?