Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / r-lib/coro issues and pull requests
#44 - Question: is coro thread safe?
Issue -
State: closed - Opened by rkrug 3 months ago
- 4 comments
#43 - programmatic async function creation
Issue -
State: open - Opened by ElianHugh 6 months ago
- 3 comments
#42 - Add website to DESCRIPTION
Pull Request -
State: open - Opened by olivroy 6 months ago
#41 - coro as an optional dependency
Issue -
State: closed - Opened by trangdata 8 months ago
- 2 comments
#40 - How to pass rcmdcheck using generators
Issue -
State: open - Opened by latot 10 months ago
- 2 comments
#39 - Async function errors should not be raised in the main thread
Issue -
State: open - Opened by king-of-poppk about 1 year ago
- 1 comment
#38 - coro upkeep 2023
Issue -
State: closed - Opened by lionel- over 1 year ago
#37 - Add support for python objects
Pull Request -
State: closed - Opened by t-kalinowski about 2 years ago
- 9 comments
#36 - Memory leak when a generator is created inside a function
Issue -
State: closed - Opened by dfalbel almost 3 years ago
- 6 comments
#35 - Use an unlikely sentinel
Issue -
State: closed - Opened by lionel- almost 3 years ago
#34 - Running coro in R scripts
Issue -
State: open - Opened by Fabrice-Clement over 3 years ago
- 2 comments
#33 - Loops and missing else branches in `async()` functions should return promises to `NULL`
Issue -
State: open - Opened by lionel- over 3 years ago
#32 - Questions about yield differences between collect and loop/for
Issue -
State: closed - Opened by mattwarkentin over 3 years ago
- 2 comments
#31 - Yield in nested iterators
Issue -
State: closed - Opened by dfalbel over 3 years ago
- 1 comment
#30 - Error when making generator a method of an R6 class
Issue -
State: closed - Opened by dfalbel over 3 years ago
- 5 comments
#29 - Some weird behaviour in async
Issue -
State: closed - Opened by dselivanov over 3 years ago
- 2 comments
#28 - Allow as_iterator extensions via S3 methods
Issue -
State: closed - Opened by dfalbel over 3 years ago
- 1 comment
#27 - Use special `quote(exhausted)` sentinel to signal iterator exhaustion
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#26 - Suspend and resume exit expressions
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#25 - Async error handling
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#24 - Handle `tryCatch()` assignments
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#23 - Support yielding within `tryCatch()`
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#22 - Rewrite flowery state machine parser
Pull Request -
State: closed - Opened by lionel- over 3 years ago
#21 - Add `async_generator()` and `await_each()`
Pull Request -
State: closed - Opened by lionel- almost 4 years ago
#20 - Add `async()` and `await()`
Pull Request -
State: closed - Opened by lionel- almost 4 years ago
#19 - Support generators taking arguments
Pull Request -
State: closed - Opened by lionel- almost 4 years ago
#18 - Export primitives for coroutine control flow
Pull Request -
State: closed - Opened by lionel- almost 4 years ago
#17 - Remove iterator abstraction from flowery
Pull Request -
State: closed - Opened by lionel- almost 4 years ago
#16 - yield_from()
Issue -
State: closed - Opened by lionel- almost 4 years ago
- 1 comment
#15 - Arity-1 generators
Issue -
State: closed - Opened by lionel- almost 4 years ago
- 2 comments
#14 - Rename `_step` functions
Issue -
State: closed - Opened by lionel- almost 4 years ago
#13 - timeline before this is available on CRAN?
Issue -
State: closed - Opened by t-kalinowski about 5 years ago
- 6 comments
#12 - make iterate() return invisibly
Pull Request -
State: closed - Opened by dfalbel about 5 years ago
#11 - %do% operator?
Issue -
State: closed - Opened by dfalbel about 5 years ago
- 2 comments
#10 - Iterate could return invisibly
Issue -
State: closed - Opened by dfalbel about 5 years ago
- 2 comments
#9 - iterate won't work if iterator was created in a pipe chain
Issue -
State: closed - Opened by dfalbel about 5 years ago
- 6 comments
#8 - make it work when the package is not loaded
Pull Request -
State: closed - Opened by dfalbel about 5 years ago
- 3 comments
#7 - iterate will not `break` if it's directly in the body
Issue -
State: closed - Opened by dfalbel about 5 years ago
#6 - Don't throw error when advancing closed iterator
Issue -
State: closed - Opened by lionel- over 6 years ago
- 3 comments
#5 - Draft iteration vignette
Pull Request -
State: closed - Opened by lionel- over 6 years ago
- 2 comments
#4 - WIP: Implement transducers
Pull Request -
State: closed - Opened by lionel- over 6 years ago
- 2 comments
#3 - WIP: Implement iterators
Pull Request -
State: closed - Opened by lionel- over 6 years ago
#2 - WIP: Implement generators
Pull Request -
State: closed - Opened by lionel- over 6 years ago
- 1 comment
#1 - Will need to think about `on.exit`
Issue -
State: closed - Opened by gaborcsardi over 6 years ago
- 21 comments