Closed rickeyvisinski-kanban closed 11 years ago
Sounds very cool, I had planned to do it as part of 0.6 and tending toward using the Iteratee sub project code (not the current IterV). I am currently doing the last bits of 0.5 - release/0.5.0 branch that are needed for a release, so its probably a good month before I could help start with that.
In the meantime the best starting place is probably SHA: 2d730be5da0908e406da0dca5b8b132a379ed119 (current branch head).
What would be especially interesting is if ResumabeIter could be better modelled by the new library (and without casting).
Any improvement under this milestone? :)
I am making progress. I have refrained from pushing my branch so far because I have been rebasing against the release/0.5 head, but I can push it and start merging.
Currently I have removed scala 2.8 support to match the supported scala versions with scalaz 7. I have began the update using IterV library to keep working as I get a better feel for Iteratees. I'm currently running down a few bugs under the new Equals.
@chris-twiner let me know if you have any comments so far.
Many thanks for your efforts. I think its best to skip the new Iteratee library entirely, it will have the same issues with ResumableIter that I'm keen not to repeat. Using IterV will be a good step into the rest of Scalaz 7.
The luminaries in scalaz seem to be moving to scala-machines as the golden child for IO, but I'll need to get to grips with that as well :)
yay!
I am planning on starting the refactoring required for scalaz seven series support and wanted to check if there previous work or thoughts on it. Thanks.