-
Notifications
You must be signed in to change notification settings - Fork 57
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
sel! can no longer be specifically macro_used in versions 0.2.3+ #69
Comments
@application-developer-DA hmm that's a case I hadn't considered. Is this impacting your project? Do you know of any others and how widespread this is? |
From a quick github search, I found this case: https://github.com/meh/cancer/blob/97829c41f0d677cf964f788b548feed38a7ffc56/src/main.rs#L62 |
@SSheldon the issue affected the project on which I work in the company, I spot the issue and fixed it (the fix was trivial after I checked the repository, changelog and commits for 2.2.3), but I decided to inform you about the issue so that you can decide whether or not to "fix" it and also as a reference for the ones who might have the same problem. |
Thanks for the heads up :) I could look into refactoring the macro to remove the need for Sounds like the damage might be done already. Will keep an eye out for it in the future, and knowing about this should make it easy to help out if anyone else runs into the issue. |
@SSheldon Read through rust-lang/rust#35896 (comment) From what I understand, you want to mark internal macros as |
The version 0.2.3 has introduced some changes in the way
sel!()
is implemented, along with the newsel_impl
macro. The changes are indeed backward compatible, but only if the crate which usesobjc
import all macros. However if the library usesobjc
and imports the macros in the following way:then an update from 0.2.2 to 0.2.3 will produce a compile-time error (
sel_impl
cannot be found).Could we consider that the change introduced in
0.2.3
is a breaking change and does it make sense to bump the minor version instead of a patch version, so that if somebody does not experience an unexpected compile time error after updating 0.2.2 to 0.2.3?The text was updated successfully, but these errors were encountered: