Reasoning:
- Better main thread support.
objc2 encoding support (allowing use in framework crates).
async support?
- Optimizations (such as the null-ptr optimization, and others).
Desired name: dispatch2, since it fits fairly well with the naming scheme (objc2, block2 and dispatch2 would all be successors to objc, block and dispatch, and would all be libraries internally, as compared to the rest of the crates we expose, which are all frameworks). I've asked for the name here, should remember to not close this issue until that repo is archived too.
Unsure how auto-generated we can feasibly be here? But the library is comparatively small compared to most frameworks, so it's probably possible to generate an initial starting point, and then refine later on.
Upstream dispatch issues:
Upstream dispatch pull requests to integrate:
Integrate ideas from:
Other TODOs:
Reasoning:
objc2encoding support (allowing use in framework crates).asyncsupport?Desired name:
dispatch2, since it fits fairly well with the naming scheme (objc2,block2anddispatch2would all be successors toobjc,blockanddispatch, and would all be libraries internally, as compared to the rest of the crates we expose, which are all frameworks). I've asked for the name here, should remember to not close this issue until that repo is archived too.Unsure how auto-generated we can feasibly be here? But the library is comparatively small compared to most frameworks, so it's probably possible to generate an initial starting point, and then refine later on.
Upstream
dispatchissues:Upstream
dispatchpull requests to integrate:Integrate ideas from:
dispatchfruity'sdispatchdispatchrdispatch2dispatchOther TODOs: