Closed PhilippMDoerner closed 4 months ago
What I'd need now is the following:
1) An explainer how to get the github workflow to work as intended (it should just run nimble test
and that should do the trick)
2) A quick yes/no if that approach seems acceptable for the given project (You mentioned you wanted to be included when it comes to project direction. Including async is pretty significant in that part)
3) ... maybe some help with rewriting examples in the README.md and listing the capabilities that we have so far :smile:
4) Maybe some additional tests, I'm pretty sure the test-suite is not fully exhaustive, though it has been a really nice guide and helping hand so far
For the test you can leave it now if it's hard for you to fix them. I think it can be fixed as other issue after this merged (You can remove current github acvtions for now)
As far as I can see lgtm. README should be rewritten tho. I think we can do them as separated another issue. I am really appreciate your hard job! well done!
hmm it seems installation issue more than test itself? https://github.com/minamorl/rex/actions/runs/8959850118/job/24605725104 (Edit: macos binary 2.0.4 seem missing for this action. I think we can ignore them)
"body": "Commit: [https://github.com/nim-lang/Nim/commit/b47747d31844c6bd9af4322efe55e24fefea544c\n\nGenerated](https://github.com/nim-lang/Nim/commit/b47747d31844c6bd9af4322efe55e24fefea544c/n/nGenerated) release binaries will be uploaded as they're made available."
Could you check if the windows implementation runs? It was previously only interrupted due to the macos one crashing
Okay, with the test-suite running through I'm comfortable merging this.
Second attempt at a merge. This time also implementing the
take
operator and async! I'll copy the description of the last PR since that still applies:On top of that with the newest version:
Subject.next
,complete
andsubscribe
procs to return futures (subscribe returns them as part ofSubscription
) which contain the "asynchronous-work"-parts of their operations and can be awaited at any later point in time. For convenience there's also appropriate blocking procs (e.g.doWork
,completeBlock
,nextBlock
etc.).