-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Dispatch / libdispatch
#77
Comments
dispatch
crate? If so, under what name?dispatch
crate?
I think this would be a good idea. Note that the types are needed for a full translation of the |
This would be incredibly useful and with the following pr being merged, it would enable a quite nice interop between ffi/objc/rust. |
- Add to CI. - Update to 2021 edition. - Appease Clippy. - Support visionOS and watchOS. - Align Cargo.toml metadata with the rest of the project. - Fix typos. Part of #77.
- Add to CI. - Update to 2021 edition. - Support visionOS and watchOS. - Align Cargo.toml metadata with the rest of the project. - Fix typos. - Appease Clippy. - Prefer `Box::into_raw` over `Box::leak`. Part of #77.
- Add to CI. - Update to 2021 edition. - Support visionOS and watchOS. - Align Cargo.toml metadata with the rest of the project. - Fix typos. - Appease Clippy. - Prefer `Box::into_raw` over `Box::leak`. - Consolidate documentation. Part of #77.
- Add to CI. - Update to 2021 edition. - Support visionOS and watchOS. - Align Cargo.toml metadata with the rest of the project. - Fix typos. - Appease Clippy. - Prefer `Box::into_raw` over `Box::leak`. - Consolidate documentation. Part of #77.
- Add to CI. - Update to 2021 edition. - Support visionOS and watchOS. - Align Cargo.toml metadata with the rest of the project. - Fix typos. - Appease Clippy. - Prefer `Box::into_raw` over `Box::leak`. - Consolidate documentation. Part of #77.
I have integrated the |
@madsmtm amazing thank you! I am pulling |
Hi @madsmtm, does resolving this issue imply that we will have |
Yeah, I'm working on figuring out hooking it up to Which is currently hard to do, since we have the extra So I'll investigate further, and try to upstream a documentation update, otherwise we might have to mark some of these functions as |
To: - Ensure that it's correct and complete. - Enable better documentation once we translate header comments too. - Allow better integration with frameworks in the future. Part of #77.
Reasoning:
objc2
encoding support (allowing use in framework crates).async
support?Desired name:
dispatch2
, since it fits fairly well with the naming scheme (objc2
,block2
anddispatch2
would all be successors toobjc
,block
anddispatch
, 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:
dispatch
fruity
'sdispatch
dispatchr
dispatch2
dispatch
Other TODOs:
The text was updated successfully, but these errors were encountered: