Skip to content
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 #import, not @import #2524

Merged
merged 1 commit into from Oct 30, 2015
Merged

use #import, not @import #2524

merged 1 commit into from Oct 30, 2015

Conversation

ianthehenry
Copy link
Contributor

As far as I can tell, there is no way to enable module support in a project that uses any Objective-C++. This means that importing the ReactiveCocoa headers -- even from a pure Objective-C file -- will result in an error on this line.

Since it's the only use of @import in the codebase, it seems nice from a consistency standpoint as well.

As far as I can tell, there is no way to enable module support
in a project that uses *any* Objective-C++. This means that
importing the ReactiveCocoa headers -- even from a pure
Objective-C file -- will result in an error on this line.

Since it's the only use of @import in the codebase, it seems nice
from a consistency standpoint as well.
@NachoSoto
Copy link
Member

This is 100% equivalent as it will get automatically converted to a module @import if they're enabled, so okay!

NachoSoto added a commit that referenced this pull request Oct 30, 2015
@NachoSoto NachoSoto merged commit 96be941 into ReactiveCocoa:master Oct 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants