play-iteratees
play-iteratees copied to clipboard
playframework
# Pull Request Checklist * [x] Have you read through the [contributor guidelines](https://www.playframework.com/contributing)? * [x] Have you signed the [Typesafe CLA](https://www.typesafe.com/contribute/cla)? * [ ] Have you [squashed your commits](https://www.playframework.com/documentation/latest/WorkingWithGit#Squashing-commits)? *...
# Pull Request Checklist * [x] Have you read through the [contributor guidelines](https://www.playframework.com/contributing)? * [x] Have you signed the [Typesafe CLA](https://www.typesafe.com/contribute/cla)? * [x] Have you [squashed your commits](https://www.playframework.com/documentation/latest/WorkingWithGit#Squashing-commits)? * [...
Release a new version of play-iteratees with Scala 2.13.0-M3 support. Depends on https://github.com/nbronson/scala-stm/issues/67.
This is not working but I thought I'd post the existing state for review. The scala-collection-compat dependency could be removed by copying some of its code into play-iteratees. scala 2.12...
This scala function has been deprecated since 2.12.0. The default implementation is empty.
From https://github.com/playframework/playframework/issues/5071 The `close()` method defined at https://github.com/playframework/playframework/blob/2.4.x/framework/src/iteratees/src/main/scala/play/api/libs/iteratee/Concurrent.scala#L461 does not appear to be used anywhere.
From https://github.com/playframework/playframework/issues/3619 At the moment `Concurrent.unicast` is really hard to use. It should often be used instead of `Concurrent.broadcast`, but I think it's just too hard to work out. I...
This shouldn't be done, for example, it breaks the following: ``` Streams.publisherToEnumerator(somePublisher) >>> Enumerator("foo") ``` If the IterateeSubscriber (created by the PublisherEnumerator) feeds EOF when the publisher is done, then...
From https://github.com/playframework/playframework/issues/1076: In the iteratees module we use `var`s in the iteratees package in what looks like a non-thread-safe way. We need to review each occurrence and possibly update it...