Releases: swiftwasm/swift
Releases · swiftwasm/swift
swift-wasm-5.8-SNAPSHOT-2023-07-06-a
[wasm] All SwiftWasm patches Co-authored-by: Max Desiatov <[email protected]> Co-authored-by: Zhuowei Zhang <[email protected]>
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-07-04-a
[installer] Do not follow an existing symbolic link when overwriting Without `-h` option, `ln` command makes a symbolic link under the existing link destination like `Toolchains/swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain/`. ``` $ ln -fs swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain swift-latest.xctoolchain $ ln -fs swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain swift-latest.xctoolchain $ tree |-- swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain | |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-latest.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain ``` So we should not follow the existing symbolic link even if it already exists.
swift-wasm-5.9-SNAPSHOT-2023-07-04-a
[test] Make KeyPath test pointer-size agnostic part 2
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-07-02-a
[installer] Do not follow an existing symbolic link when overwriting Without `-h` option, `ln` command makes a symbolic link under the existing link destination like `Toolchains/swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain/`. ``` $ ln -fs swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain swift-latest.xctoolchain $ ln -fs swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain swift-latest.xctoolchain $ tree |-- swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain | |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-latest.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain ``` So we should not follow the existing symbolic link even if it already exists.
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-6-30-a
[installer] Do not follow an existing symbolic link when overwriting Without `-h` option, `ln` command makes a symbolic link under the existing link destination like `Toolchains/swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain/`. ``` $ ln -fs swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain swift-latest.xctoolchain $ ln -fs swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain swift-latest.xctoolchain $ tree |-- swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain | |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain |-- swift-latest.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain ``` So we should not follow the existing symbolic link even if it already exists.
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-6-25-a
[Concurrency] Fix signature mismatch of _startTaskOnMainActor The function is defined in Task.cpp with a void return type, but referenced in Task.swift with an pointer return type.
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-6-25-b
[Concurrency] Fix signature mismatch of _startTaskOnMainActor The function is defined in Task.cpp with a void return type, but referenced in Task.swift with an pointer return type.
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-06-20-a
Merge pull request #5537 from swiftwasm/katei/merge-main-2023-06-20 Merge main 2023-06-20
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-06-19-a
Merge pull request #5534 from swiftwasm/main [pull] swiftwasm from main
swift-wasm-DEVELOPMENT-SNAPSHOT-2023-06-15-a
Merge pull request #5525 from swiftwasm/main [pull] swiftwasm from main