---

yaml
---
r: 284031
b: refs/heads/master-next
c: 5dec537
h: refs/heads/master
i:
  284029: f82580e
  284027: 4ad9e57
  284023: 757092e
  284015: 99ab5a7
  283999: cb04d4c
  283967: 35b3ced
  283903: 6d80e22

Author: Davide Italiano

[refs]

@@ -1,6 +1,6 @@
 ---
 refs/heads/master: 913a1f57faca996135623c287c09060d8d0532ec
-refs/heads/master-next: 0e60b633b58e48c255912dec1fb0356d6cb42d49
+refs/heads/master-next: 5dec5371733e4668cb16e79610050321cc778536
 refs/tags/osx-passed: b6b74147ef8a386f532cf9357a1bde006e552c54
 refs/tags/swift-2.2-SNAPSHOT-2015-12-01-a: 6bb18e013c2284f2b45f5f84f2df2887dc0f7dea
 refs/tags/swift-2.2-SNAPSHOT-2015-12-01-b: 66d897bfcf64a82cb9a87f5e663d889189d06d07

branches/master-next/CHANGELOG.md

@@ -6,7 +6,6 @@ CHANGELOG
 
 | Contents               |
 | :--------------------- |
-| [Swift Next](#swift-next) |
 | [Swift 5.1](#swift-51) |
 | [Swift 5.0](#swift-50) |
 | [Swift 4.2](#swift-42) |
@@ -23,162 +22,12 @@ CHANGELOG
 
 </details>
 
-Swift Next
-----------
-
-* [SR-6118][]:
-
-  Subscripts can now declare default arguments:
-
-  ```swift
-  struct Subscriptable {
-    subscript(x: Int, y: Int = 0) {
-      ...
-    }
-  }
-
-  let s = Subscriptable()
-  print(s[0])
-  ```
-
-**Add new entries to the top of this section, not here!**
-
 Swift 5.1
 ---------
 
-* [SE-0244][]:
-
-  Functions can now hide their concrete return type by declaring what protocols
-  it conforms to instead of specifying the exact return type:
-
-  ```
-  func makeMeACollection() -> some Collection {
-    return [1, 2, 3]
-  }
-  ```
-
-  Code that calls the function can use the interface of the protocol, but
-  does not have visibility into the underlying type.
-
-* [SE-0254][]:
-
-  Subscripts can now be declared `static` or (inside classes) `class`.
-
-* [SE-0252][]:
-
-  The existing `@dynamicMemberLookup` attribute has been extended with a
-  support for strongly-typed keypath implementations:
-
-  ```swift
-  @dynamicMemberLookup
-  struct Lens<T> {
-    let getter: () -> T
-    let setter: (T) -> Void
-
-    var value: T {
-      get {
-        return getter()
-      }
-      set {
-        setter(newValue)
-      }
-    }
-
-    subscript<U>(dynamicMember keyPath: WritableKeyPath<T, U>) -> Lens<U> {
-      return Lens<U>(
-          getter: { self.value[keyPath: keyPath] },
-          setter: { self.value[keyPath: keyPath] = $0 })
-    }
-  }
-  ```
-
-* [SR-8546][], [SR-9043][]:
-
-  More thorough checking has been implemented for restrictions around
-  escaping closures capturing `inout` parameters or values of noescape type.
-  While most code should not be affected, there are edge cases where
-  the Swift 5.0 compiler would accept code violating these restrictions.
-  This could result in runtime crashes or silent data corruption.
-  
-  An example of invalid code which was incorrectly accepted by the Swift 5.0
-  compiler is an `@escaping` closure calling a local function which
-  references an `inout` parameter from an outer scope:
-
-  ```swift
-  struct BadCaptureExample {
-    var escapingClosure: () -> ()
-
-    mutating func takesInOut(_ x: inout Int) {
-      func localFunction() {
-        x += 1
-      }
-
-      escapingClosure = { localFunction() }
-    }
-  }
-  ```
-
-  The compiler now correctly diagnoses the above code by pointing out that
-  the capture of `x` by `localFunction()` is invalid, since `localFunction()`
-  is referenced from an `@escaping` closure.
-
-  This also addresses certain cases where the compiler incorrectly diagnosed
-  certain code as invalid, when in fact no violation of restrictions had
-  taken place. For example,
-
-  ```swift
-  func takesNoEscape(_ fn: () -> ()) {
-    func localFunction() {
-      fn()
-    }
-
-    { localFunction() }()
-  }
-  ```
-
-* [SR-2672][]:
-
-  Conversions between tuple types are now fully implemented.
-  Previously, the following would diagnose an error:
-
-  ```swift
-  let values: (Int, Int) = (10, 15)
-  let converted: (Int?, Any) = values
-
-* [SE-0242][]:
-
-  The memberwise initializer for structures now provide default values for variables that hold default expressions.
-
-  ```swift
-  struct Dog {
-    var name = "Generic dog name"
-    var age = 0
-
-    // The synthesized memberwise initializer
-    init(name: String = "Generic dog name", age: Int = 0)
-  }
-
-  let sparky = Dog(name: "Sparky") // Dog(name: "Sparky", age: 0)
-  ```
-
 * [SE-0068][]:
 
-  It is now possible to use `Self` to refer to the innermost nominal
-  type inside struct, enum and class declarations. For example, the
-  two method declarations inside this struct are equivalent:
-  
-  ```swift
-  struct Box<Value> {
-    func transform1() -> Self { return self }
-    func transform2() -> Box<Value> { return self }
-  }
-  ```
-
-  In classes, `Self` is the dynamic type of the `self` value, as before.
-  Existing restrictions on `Self` in declaration types still apply;
-  that is, `Self` can only appear as the return type of a method.
-  However, `Self` can now be used inside the body of a method
-  without limitation.
+  `Self` can now be used inside member functions and for function arguments of structs and enums to refer to the containing type.
 
 * [SR-7799][]:
 
@@ -197,12 +46,12 @@ Swift 5.1
   }
   ```
 
-* `weak` and `unowned` stored properties no longer inhibit the
-   automatic synthesis of `Equatable` or `Hashable` conformance.
+* `weak` and `unowned` variables can now be used inside types that
+   declare `Equatable` or `Hashable` conformance.
 
 * [SR-2688][]:
 
-  An `@autoclosure` parameter can now be declared with a typealias type.
+  An `@autoclosure` closure can now be a typealias.
 
   ```swift
   class Foo {
@@ -213,12 +62,10 @@ Swift 5.1
 
 * [SR-7601][]:
 
-  Methods declared `@objc` inside a class can now return `Self`:
+  Functions marked with `@objc` can now return `Self`
 
   ```swift
-  class MyClass : NSObject {
-    @objc func clone() -> Self { return self }
-  }
+  @objc func returnDynamicSelf() -> Self { return self }
   ```
 
 * [SR-2176][]:
@@ -262,8 +109,6 @@ Swift 5.1
 Swift 5.0
 ---------
 
-### 2019-03-25 (Xcode 10.2)
-
 * [SE-0235][]:
 
   The standard library now contains a `Result` type for manually propagating errors.
@@ -524,6 +369,8 @@ Swift 5.0
   }
   ```
 
+**Add new entries to the top of this section, not here!**
+
 Swift 4.2
 ---------
 
@@ -7664,11 +7511,7 @@ Swift 1.0
 [SE-0228]: <https://github.com/apple/swift-evolution/blob/master/proposals/0228-fix-expressiblebystringinterpolation.md>
 [SE-0230]: <https://github.com/apple/swift-evolution/blob/master/proposals/0230-flatten-optional-try.md>
 [SE-0235]: <https://github.com/apple/swift-evolution/blob/master/proposals/0235-add-result.md>
-[SE-0242]: <https://github.com/apple/swift-evolution/blob/master/proposals/0242-default-values-memberwise.md>
-[SE-0244]: <https://github.com/apple/swift-evolution/blob/master/proposals/0244-opaque-result-types.md>
 [SE-0245]: <https://github.com/apple/swift-evolution/blob/master/proposals/0245-array-uninitialized-initializer.md>
-[SE-0252]: <https://github.com/apple/swift-evolution/blob/master/proposals/0252-keypath-dynamic-member-lookup.md>
-[SE-0254]: <https://github.com/apple/swift-evolution/blob/master/proposals/0254-static-subscripts.md>
 
 [SR-106]: <https://bugs.swift.org/browse/SR-106>
 [SR-419]: <https://bugs.swift.org/browse/SR-419>
@@ -7682,16 +7525,12 @@ Swift 1.0
 [SR-2388]: <https://bugs.swift.org/browse/SR-2388>
 [SR-2394]: <https://bugs.swift.org/browse/SR-2394>
 [SR-2608]: <https://bugs.swift.org/browse/SR-2608>
-[SR-2672]: <https://bugs.swift.org/browse/SR-2672>
 [SR-2688]: <https://bugs.swift.org/browse/SR-2688>
 [SR-4248]: <https://bugs.swift.org/browse/SR-4248>
 [SR-5581]: <https://bugs.swift.org/browse/SR-5581>
 [SR-5719]: <https://bugs.swift.org/browse/SR-5719>
-[SR-6118]: <https://bugs.swift.org/browse/SR-6118>
 [SR-7139]: <https://bugs.swift.org/browse/SR-7139>
 [SR-7251]: <https://bugs.swift.org/browse/SR-7251>
 [SR-7601]: <https://bugs.swift.org/browse/SR-7601>
 [SR-7799]: <https://bugs.swift.org/browse/SR-7799>
 [SR-8109]: <https://bugs.swift.org/browse/SR-8109>
-[SR-8546]: <https://bugs.swift.org/browse/SR-8546>
-[SR-9043]: <https://bugs.swift.org/browse/SR-9043>

branches/master-next/CMakeLists.txt

@@ -497,7 +497,7 @@ else()
   swift_common_unified_build_config(SWIFT)
 endif()
 
-get_filename_component(SWIFT_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR} REALPATH)
+set(SWIFT_SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}")
 set(SWIFT_BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}")
 set(SWIFT_CMAKE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/cmake/modules")
 set(SWIFT_MAIN_INCLUDE_DIR "${SWIFT_SOURCE_DIR}/include")

branches/master-next/benchmark/CMakeLists.txt

@@ -253,10 +253,6 @@ set(BENCHOPTS_MULTITHREADED
     "-whole-module-optimization" "-num-threads" "4")
 set(BENCHOPTS_SINGLEFILE "")
 
-option(SWIFT_BENCHMARK_USE_OS_LIBRARIES
-  "Runtime link against the Swift libraries on the target (/usr/lib/swift)."
-  FALSE)
-
 configure_build()
 
 #===-----------------------------------------------------------------------===#
@@ -272,18 +268,10 @@ configure_sdks()
 message("--")
 message("-- Swift Benchmark Suite:")
 message("--   SWIFT_BENCHMARK_BUILT_STANDALONE = ${SWIFT_BENCHMARK_BUILT_STANDALONE}")
-message("--   SWIFT_BENCHMARK_USE_OS_LIBRARIES = ${SWIFT_BENCHMARK_USE_OS_LIBRARIES}")
-message("--   SWIFT_EXEC         = ${SWIFT_EXEC}")
-message("--   SWIFT_LIBRARY_PATH = ${SWIFT_LIBRARY_PATH}")
-if (SWIFT_RPATH_BASE)
-message("--   SWIFT_RPATH_BASE   = ${SWIFT_RPATH_BASE}")
-endif()
-if (SWIFT_RPATH)
-message("--   SWIFT_RPATH        = ${SWIFT_RPATH}")
-message("---  ** WARNING ** Benchmarking against Swift-in-the-OS")
-endif()
-message("--   CLANG_EXEC         = ${CLANG_EXEC}")
+message("--   SWIFT_EXEC = ${SWIFT_EXEC}")
 message("--   SWIFT_BENCHMARK_EXTRA_FLAGS = ${SWIFT_BENCHMARK_EXTRA_FLAGS}")
+message("--   SWIFT_LIBRARY_PATH = ${SWIFT_LIBRARY_PATH}")
+message("--   CLANG_EXEC = ${CLANG_EXEC}")
 message("--   SWIFT_OPTIMIZATION_LEVELS = ${SWIFT_OPTIMIZATION_LEVELS}")
 message("--   ONLY_PLATFORMS = ${ONLY_PLATFORMS}")
 message("--   PAGE_ALIGNMENT_OPTION = ${PAGE_ALIGNMENT_OPTION}")

branches/master-next/benchmark/README.md

@@ -28,11 +28,6 @@ flags:
 OS X benchmark driver binaries are placed in `bin` alongside `swiftc`.
 Additional platform binaries are placed in the `benchmark/bin` build directory.
 
-The required Swift standard library dylibs are placed in `lib`. The
-drivers dynamically link Swift standard library dylibs from a path
-relative to their run-time location (../lib/swift) so the standard
-library should be distributed alongside them.
-
 Building Independently
 ----------------------
 
@@ -48,19 +43,15 @@ The following build options are available:
 * `-DSWIFT_LIBRARY_PATH`
     * An absolute path to the Swift standard library to use during compilation
       (default: `swiftc_directory`/../lib/swift)
-* `-DSWIFT_DARWIN_XCRUN_TOOLCHAIN`
-    * The Xcode toolchain to use when invoking `xcrun` to find `clang`.
-      (default: XcodeDefault)
 * `-DONLY_PLATFORMS`
     * A list of platforms to build the benchmarks for
       (default: "macosx;iphoneos;appletvos;watchos")
 * `-DSWIFT_OPTIMIZATION_LEVELS`
     * A list of Swift optimization levels to build against
       (default: "O;Onone;Osize")
-* `-DSWIFT_BENCHMARK_USE_OS_LIBRARIES`
-    * Enable this option to link the benchmark binaries against the target
-      machine's Swift standard library and runtime installed with the OS.
-    (default: OFF)
+* `-DSWIFT_BENCHMARK_EMIT_SIB`
+    * A boolean value indicating whether .sib files should be generated
+      alongside .o files (default: FALSE)
 
 The following build targets are available:
 
@@ -75,40 +66,13 @@ Build steps (with example options):
 1. `$ cd benchmark`
 2. `$ mkdir build`
 3. `$ cd build`
-4. `$ cmake ../benchmark -G Ninja -DSWIFT_EXEC=[path to built swiftc]`
-5. `$ ninja swift-benchmark-macosx-x86_64`
-
-Benchmark binaries are placed in `bin`.
-
-The binaries dynamically link Swift standard library dylibs from a
-path determined by the configuration. If `SWIFT_LIBRARY_PATH` is set,
-they link against the absolute path provided, regardless of where the
-binaries are installed. Otherwise, the runtime library path is
-relative to the benchmark binary at the time it was executed
-(`@executable_path/../lib/swift/<platform>`).
-
-For example, to benchmark against a locally built `swiftc`, including
-any standard library changes in that build, you might configure using:
-
-    cmake ../benchmark -G Ninja -DSWIFT_EXEC=<src>/swift/build/swift-macosx-x86_64/bin/swiftc
-    ninja swift-benchmark-iphoneos-arm64
-
-To build against the installed Xcode, simply omit SWIFT_EXEC:
-
-    cmake ../benchmark -G Ninja
-    ninja swift-benchmark-iphoneos-arm64
-
-In both examples above, to run the benchmarks on a device, the dynamic
-libraries must then be copied onto the device into the library path
-relative to `swiftc`. To benchmark against the target machine's
-installed libraries instead, enable
-`SWIFT_BENCHMARK_USE_OS_LIBRARIES`.
-
-    cmake ../benchmark -G Ninja -DSWIFT_BENCHMARK_USE_OS_LIBRARIES=ON
-    ninja swift-benchmark-iphoneos-arm64
+4. `$ cmake ..`
+5. `$ make -j8 swift-benchmark-macosx-x86_64`
 
-This will reflect the performance of the Swift standard library
-installed on the device, not the one included in the Swift root.
+Benchmark driver binaries are placed in `build/bin` and the required Swift
+standard library dylibs are placed in `build/lib`. The drivers dynamically link
+Swift standard library dylibs from a path relative to their location
+(../lib/swift) so the standard library should be distributed alongside them.
 
 Using the Benchmark Driver
 --------------------------