Skip to content

[swift-3.0-branch] Implementing SE-0137 #4361

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 5 commits into from
Aug 18, 2016

Conversation

moiseev
Copy link
Contributor

@moiseev moiseev commented Aug 17, 2016

What's in this pull request?

  • Explanation: Implementation for SE-0137. Commits are cherry-picked from the individual PRs opened against master.
  • Scope of Issue: Applying this change will result in several new deprecation warnings during compilation, but no code will stop compiling. Most of the deprecation attributes have a hint for the XCode on how to fix it.
  • Origination: Last minute changes to avoid committing to the current design of protocols in the standard library.
  • Risk: Minimal
  • Reviewed By: Dave Abrahams
  • Testing: Ran the existing test suite.
  • Directions for QA: N/A

rdar://problem/27894275


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 test and merge
OS X platform @swift-ci Please test OS X platform
OS X platform @swift-ci Please benchmark
Linux platform @swift-ci Please test Linux platform

Lint Testing

Language Comment
Python @swift-ci Please Python lint

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

@moiseev
Copy link
Contributor Author

moiseev commented Aug 17, 2016

@swift-ci Please smoke test

@moiseev
Copy link
Contributor Author

moiseev commented Aug 17, 2016

@swift-ci Please smoke test

@moiseev
Copy link
Contributor Author

moiseev commented Aug 18, 2016

@swift-ci Please smoke test Linux platform

@rintaro
Copy link
Member

rintaro commented Aug 18, 2016

I think, #4214 is also needed. (to pass the long-test)

@tkremenek
Copy link
Member

@swift-ci test

Dave Abrahams and others added 5 commits August 18, 2016 11:01
Using them is always a mistake; the user should choose the corresponding
Collection protocol instead.
It's important to let people know that, in contrast with existing
practice in other frameworks, we really are going to remove the
deprecated API, and soon.
We know its API is
inadequate (https://bugs.swift.org/browse/SR-1260?jql=text%20~%20%22StringInterpolationConvertible%22)
and don't want to be constrained to supporting it in future versions.
…ertible

Since the ExpressibleByStringInterpolation protocol is also deprecated
now, it makes little sense to suggest using it instead of
StringInterpolationConvertible. Instead, the message now recommends
considering an init(_:String).
See
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160808/026171.html
for some more details.
…ng. (swiftlang#4214)

...and make sure we're in that mode for SIL inputs and for sil-opt and
sil-extract, even when working with AST types and declarations rather
than SIL types.

Without this, we get zillions of deprecation warnings coming out of
the validation tests SIL/parse_stdlib_*.sil, which dump the standard
library and then attempt to re-parse it. This has been causing the
"long" tests to take, well, too long.
@moiseev
Copy link
Contributor Author

moiseev commented Aug 18, 2016

Good catch, @rintaro! Thanks.

@moiseev
Copy link
Contributor Author

moiseev commented Aug 18, 2016

Cherry picked the #4214 commit and removed the renaming of Streamable to TextOutputStreamable for now. Will include that one separately.
@swift-ci Please test

@tkremenek
Copy link
Member

Enough tests are passing to merge.

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.

4 participants