Skip to content

[ClangImporter] Predefine __swift__ in imported (Obj)C code. #4510

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

Merged
merged 1 commit into from
Aug 26, 2016

Conversation

jrose-apple
Copy link
Contributor

This macro expands to a numeric value representing the current Swift language version; for Swift 3.1.2, it would be 30102.

See discussion in https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20160822/002754.html.

rdar://problem/26921435


Before merging this pull request to apple/swift repository:

  • Test pull request on Swift continuous integration.

Triggering Swift CI

The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:

Smoke Testing

Platform Comment
All supported platforms @swift-ci Please smoke test
All supported platforms @swift-ci Please smoke test and merge
OS X platform @swift-ci Please smoke test OS X platform
Linux platform @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library only for macOS. Simulator standard libraries and
    device standard libraries are not built.
  3. lldb is not built.
  4. The test and validation-test targets are run only for macOS. The optimized
    version of these tests are not run.

A smoke test on Linux does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library incrementally.
  3. lldb is built incrementally.
  4. The swift test and validation-test targets are run. The optimized version of these
    tests are not run.
  5. lldb is tested.

Validation Testing

Platform Comment
All supported platforms @swift-ci Please test
All supported platforms @swift-ci Please clean test
All supported platforms @swift-ci Please test and merge
OS X platform @swift-ci Please test OS X platform
OS X platform @swift-ci Please clean test OS X platform
OS X platform @swift-ci Please benchmark
Linux platform @swift-ci Please test Linux platform
Linux platform @swift-ci Please clean test Linux platform

Lint Testing

Language Comment
Python @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@jrose-apple
Copy link
Contributor Author

@bitjammer, this is your code I'm generalizing. Can you double-check that I did it right, especially since we don't have a good way to write tests for __SWIFT_COMPILER_VERSION?

This macro expands to a numeric value representing the current Swift
language version; for Swift 3.1.2, it would be 30102.

See discussion in https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20160822/002754.html.

rdar://problem/26921435
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

@DougGregor
Copy link
Member

LGTM

@bitjammer
Copy link
Contributor

Looks reasonable to me, @jrose-apple.

@jrose-apple jrose-apple merged commit 5ffb151 into swiftlang:master Aug 26, 2016
@jrose-apple jrose-apple deleted the __swift__ branch August 26, 2016 01:26
jrose-apple added a commit to jrose-apple/swift that referenced this pull request Aug 26, 2016
…ng#4510)

This macro expands to a numeric value representing the current Swift
language version; for Swift 3.1.2, it would be 30102.

See discussion in https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20160822/002754.html.

rdar://problem/26921435
(cherry picked from commit 5ffb151)
artemcm added a commit to artemcm/swift that referenced this pull request Jul 31, 2024
Leaving behind an un-versioned `__swift__` macro.
Originally added in swiftlang#4510 (rdar://26921435) following a discussion in https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20160822/002754.html, the versioned macro was used to allow clients primarily to ready their existing ObjectiveC code for Swift 2 -> Swift 3 transition.

Now that neither one of those versions is a supported language mode and we have versioned APINotes support, and we do not currently know of clients that rely on the version carried by this macro, we would like to deprecate it, leaving behind the un-versioned `-D__swift__`.

The reason for the deprecation is that it is likely that in a build with multiple targets which have very similar configuration aside from Swift language version, they would not be able to share module dependencies due to the mismatch in the macro value.
artemcm added a commit to artemcm/swift that referenced this pull request Aug 1, 2024
Leaving behind an un-versioned `__swift__` macro.
Originally added in swiftlang#4510 (rdar://26921435) following a discussion in https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20160822/002754.html, the versioned macro was used to allow clients primarily to ready their existing ObjectiveC code for Swift 2 -> Swift 3 transition.

Now that neither one of those versions is a supported language mode and we have versioned APINotes support, and we do not currently know of clients that rely on the version carried by this macro, we would like to deprecate it, leaving behind the un-versioned `-D__swift__`.

The reason for the deprecation is that it is likely that in a build with multiple targets which have very similar configuration aside from Swift language version, they would not be able to share module dependencies due to the mismatch in the macro value.
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.

3 participants