-
Notifications
You must be signed in to change notification settings - Fork 35
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
Use objc2
and its framework crates
#74
Conversation
This catches a few extra error cases related to paths, as well as making it easier to ensure that memory management rules are upheld. Concretely, it fixes a leak in the passing of the `NSArray` to `writeObjects`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened to objc, is it not communicative? Seems like you're the maintainer of the objc2 crates, is that correct?
Apologies, should've given a more detailed explanation, assumed you knew it already. I'm the maintainer of Did that give a bit more insight? Feel free to ask about anything else that's unclear! |
Doing the same things as winit makes a lot of sense since alacirtty is a consumer of both this crate and winit. |
Sounds like you just got ignored lol. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@madsmtm I'd assume you've tested this against some client? Or used the examples to confirm it actually works?
I have no way to test macOS myself, so I'll hold off merging until I can get a confirmation on this.
The Happy to add some tests in the process if given guidance. |
Shouldn't really be possible, so doesn't need testing. Thanks for the help. |
`objc2` / `objc2-foundation` is much more type-safe than `cocoa`, and automatically ensures that memory management-rules are upheld. See also alacritty/copypasta#74.
`objc2` / `objc2-foundation` is much more type-safe than `cocoa`, and automatically ensures that memory management-rules are upheld. See also alacritty/copypasta#74.
This catches a few extra error cases related to paths, as well as making it easier to ensure that memory management rules are upheld.
Concretely, it fixes a leak in the passing of the
NSArray
towriteObjects
.