swift-developers-japan
main / wasm
1
1
1
1
1 1
subscript(dynamicMember name: String) -> ((ConvertibleToJSValue...) -> JSValue)? が呼ばれて、thisがレシーバでバインドされるんですが https://github.com/swiftwasm/JavaScriptKit/blob/4b7981bc1b81a1f25e7aca851866d55913657d61/Sources/JavaScriptKit/FundamentalObjects/JSObject.swift#L34-L40 JSFunction になってしまって、JSFunctionのcallAsFunctionで実行されるのでthisがバインドされないんですよね https://github.com/swiftwasm/JavaScriptKit/blob/4b7981bc1b81a1f25e7aca851866d55913657d61/Sources/JavaScriptKit/FundamentalObjects/JSFunction.swift#L21 
1 
2
1
.pkgによるswift-latest.xctoolchainシンボリックリンクの作成、既にシンボリックリンクが存在するとシンボリックリンクが指す先に新しいシンボリックリンクを作ってしまう。 https://github.com/swiftwasm/swift/blob/swiftwasm/utils/darwin-installer-scripts/postinstall#L16 これを避けるためにln -fhs …とかに変えるべき。 
1 1
1
3
破壊的変更注意
.define("CMARK_THREADING", to: "0", .when(platforms: [.wasi])) で上書きすればいけるような気もしてきました．
2
❯ docker run -it --rm -v $(pwd):/$(basename $(pwd)) -t swift:5.9 /bin/bash root@5aaf21fbf0d1:/# swift experimental-sdk install https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip Swift SDK bundle successfully downloaded from `https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip`. swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip is assumed to be an archive, unpacking... Swift SDK bundle at `https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip` successfully installed. root@5aaf21fbf0d1:/# swift experimental-sdk list 5.9.2-RELEASE-wasm
❯ docker run -it --rm -v $(pwd):/$(basename $(pwd)) -t swift:5.10 /bin/bash root@59c43fdac52e:/# swift experimental-sdk install https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip Downloading a Swift SDK bundle archive from `https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip`... Swift SDK bundle archive successfully downloaded from `https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip`. Swift SDK bundle at `https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.2-RELEASE/swift-wasm-5.9.2-RELEASE-ubuntu22.04_x86_64.artifactbundle.zip` is assumed to be an archive, unpacking... Error: gzip: stdin has more than one entry--rest ignored tar: Child returned status 2 tar: Error is not recoverable: exiting now 
❯ swift build --target FoundationEssentials --experimental-swift-sdk 5.9.2-RELEASE-wasm Building for debugging... /Users/iceman/Downloads/swift-foundation-main/.build/checkouts/swift-syntax/Sources/SwiftCompilerPlugin/CompilerPlugin.swift:103:19: error: cannot find 'dup' in scope let inputFD = dup(fileno(stdin)) ^~~ /Users/iceman/Downloads/swift-foundation-main/.build/checkouts/swift-syntax/Sources/SwiftCompilerPlugin/CompilerPlugin.swift:117:20: error: cannot find 'dup' in scope let outputFD = dup(fileno(stdout)) ^~~ /Users/iceman/Downloads/swift-foundation-main/.build/checkouts/swift-syntax/Sources/SwiftCompilerPlugin/CompilerPlugin.swift:124:11: error: cannot find 'dup2' in scope guard dup2(fileno(stderr), fileno(stdout)) >= 0 else { ^~~~ 
enum E { case c(Int) @available(*, unavailable) static func c(_: Int) -> E { fatalError() } } func check(e: E) { switch e { case .c(_): break } } <stdin>:3:42: error: invalid redeclaration of 'c' 1 │ enum E { 2 │ case c(Int) 3 │ @available(*, unavailable) static func c(_: Int) -> E { fatalError() } │ ╰─ error: invalid redeclaration of 'c' 4 │ } 5 │ 
Watcher, bundler, and test runner for your SwiftWasm apps - swiftwasm/carton
./Bundle/index.mjsがこんな感じになってると良いのかな import { SwiftRuntime } from "./JavaScriptKit_resource/index.mjs" export function init() { const importObject = { javascriptkit: SwiftRuntime.importObjects } const { instance } = await WebAssembly.instantiate(..., importObject) return instance.exports } 
Package.swift では real target に [.wasi] と mock target に allPlatforms.except([.wasi]) を指定しておけば Bool のフラグなしで解決する話だったりはしないですか？(ビルド時のターゲット triple で切り替わる感じで) https://github.com/apple/swift-package-manager/issues/4479
Package.swift では real target に [.wasi] と mock target に allPlatforms.except([.wasi]) を指定しておけば Bool のフラグなしで解決する話だったりはしないですか？(ビルド時のターゲット triple で切り替わる感じで) https://github.com/apple/swift-package-manager/issues/4479
[omochi@omochi-mbp swift-react (main *=)]$ swift experimental-sdk list DEVELOPMENT-SNAPSHOT-2024-04-03-a-wasm [omochi@omochi-mbp swift-react (main *=)]$ swift build --triple wasm32-unknown-wasi --build-tests \ -Xswiftc -static-stdlib \ -Xswiftc -Xclang-linker -Xswiftc -mexec-model=reactor \ -Xlinker --export-if-defined=main \ --disable-build-manifest-caching warning: 'swift-algorithms': found 1 file(s) which are unhandled; explicitly declare them as resources or exclude from the target /Users/omochi/github/omochi/swift-react/.build/checkouts/swift-algorithms/Sources/Algorithms/Documentation.docc Building for debugging... In file included from /Users/omochi/github/omochi/swift-react/.build/checkouts/JavaScriptKit/Sources/_CJavaScriptKit/_CJavaScriptKit.c:1: /Users/omochi/github/omochi/swift-react/.build/checkouts/JavaScriptKit/Sources/_CJavaScriptKit/include/_CJavaScriptKit.h:4:10: fatal error: 'stdlib.h' file not found 4 | #include <stdlib.h> | ^~~~~~~~~~ 1 error generated. [0/26] Write swift-version-37CF2ABA3CB73B3C.txt 
$ swift run carton test --environment browser だといけた
throws な事自体はあまり違和感はないかな サーバサイドで普段から大量の async throws にまみれているから・・・ 
1
final class JavaScriptKitTests: XCTestCase { func testClosureAsFunction() throws { let clo = JSClosure { (_) in return 7.jsValue } let obj = try JSObject.mustConstruct(from: clo.jsValue) XCTAssertFalse(obj is JSFunction) let fn = clo.asFunction() let ret = try Int.mustConstruct(from: try fn()) XCTAssertEqual(ret, 7) } } extension JSClosure { #if USES_JAVASCRIPT_KIT_MOCK public func asFunction() -> JSThrowingFunction { let fn = native as! JSNativeFunction return JSFunction(native: fn).throws } #else public func asFunction() -> JSThrowingFunction { var buffer: JSValue = Array<Int>([0]).jsValue buffer[0] = self.jsValue let fn = JSFunction.unsafeConstruct(from: buffer[0]) return fn.throws } #endif }
WebMock を実装してて困った。 public class WebEventTarget: JSNativeObject { public init() { } private var listeners: [String: [JSFunction]] = [:] public func addEventListener(_ type: String, _ listener: JSFunction) { var lns = self.listeners[type] ?? [] if lns.contains(listener) { return } lns.append(listener) self.listeners[type] = lns } public func removeEventListener(_ type: String, _ listener: JSFunction) { guard var lns = self.listeners[type] else { return } lns.removeAll { $0 == listener } self.listeners[type] = lns } public func dispatchEvent(_ event: WebEvent) -> Bool { guard let lns = self.listeners[event.type] else { return true } for ln in lns { ln(event) } return true }
public func asFunction() -> JSThrowingFunction { var buffer: JSValue = Array<Int>([0]).jsValue buffer[0] = self.jsValue let fn = JSFunction.unsafeConstruct(from: buffer[0]) return fn.throws }
func testState() throws { struct Content: Component { @State var count = 0 func render() -> Node { return div { "\(count)" button( listeners: [ "click": Function { (ev) in count += 1 } ] ) } } } let body = try document.createElement("body") let root = ReactRoot(element: body) root.render( node: Content() ) XCTAssertPrint(body, """ <body> <div> 0 <button /> </div> </body> """) let btn: JSHTMLElement = try XCTUnwrap( root.root? .find { $0.tagElement?.tagName == "button" }? .dom?.asHTMLElement() ) try btn.click() XCTAssertPrint(body, """ <body> <div> 1 <button /> </div> </body> """) } ちょっとそれっぽくなってきた（↑このテストが通った） 
3
1 1
1
1 I faced a few different issues while trying to get this working, if any of these aren't already known I'd be happy to split them out into separate topics or GitHub issues. Hiccups My fir...
1
#7341 Explanation: swift build --build-tests fails on WASI after the experimental summary output, which is introduced in 5.10. This affects not only experimental-summary mode but also the defau...
$ swift sdk が手元でもCIでも動いた。ドキュメントも更新した。 https://github.com/omochi/swift-react/pull/94 artifact bundle の選び方の説明文が変わった。
5
1
-lto=llvm-full -experimental-hermetic-seal-at-link つけたらビルドできなかった・・・ wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/Chunked.swift.o: undefined symbol: swift_deallocObject wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/AdjacentPairs.swift.o: undefined symbol: swift_release wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/Keyed.swift.o: undefined symbol: swift_bridgeObjectRelease wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/Keyed.swift.o: undefined symbol: swift_bridgeObjectRelease wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/AdjacentPairs.swift.o: undefined symbol: swift_release wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/Algorithms.build/Chunked.swift.o: undefined symbol: swift_deallocObject wasm-ld: error: /Users/omochi/github/omochi/swift-string-counter-web/.build/wasm32-unknown-wasi/release/React.build/ChildrenBuilder.swift.o: undefined symbol: $sytWV clang: error: linker command failed with exit code 1 (use -v to see invocation) [10/11] Linking StringCounter.wasm .build ディレクトリを一旦消したら別のエラーになりませんか？ビルドディレクトリに *.swift.o ファイルが見つからないというようなエラーに． そして SwiftPM だと最近 LTO を有効にするための --experimental-lto-mode=full みたいなのが追加されたみたいなので，-Xswiftc -lto=llvm-full じゃなくてこっちのフラグで指定したらどうなりますか？ https://github.com/apple/swift-package-manager/pull/6891/fileswasm-ld: error: /home/kebo/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2024-05-02-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2024-05-02-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/wasm32/swiftrt.o: undefined symbol: swift_addNewDSOImage wasm-ld: error: /home/kebo/swift-string-counter-web/.build/wasm32-unknown-wasi/debug/_CJavaScriptKit.build/_CJavaScriptKit.c.o: undefined symbol: _call_host_function_impl wasm-ld: error: /home/kebo/swift-string-counter-web/.build/wasm32-unknown-wasi/debug/_CJavaScriptKit.build/_CJavaScriptKit.c.o: undefined symbol: _free_host_function_impl wasm-ld: error: /home/kebo/swift-string-counter-web/.build/wasm32-unknown-wasi/debug/_CJavaScriptKit.build/_CJavaScriptKit.c.o: undefined symbol: _library_features clang: error: linker command failed with exit code 1 (use -v to see invocation) 1
2
1
1
1
#7341 Explanation: swift build --build-tests fails on WASI after the experimental summary output, which is introduced in 5.10. This affects not only experimental-summary mode but also the defau...
test.js を返す制御ってどこですか？ configuration.entrypoint に test.js って書いてあるんだけど、 routerの実装で configuration.entrypoint を読んでる部分がないので、 配送できないように見える 実際 index.html は取れるけど test.js は取れない [omochi@omochi-mbp swift-react (swift510 *%)]$ curl -v http://127.0.0.1:8080/ * Trying 127.0.0.1:8080... * Connected to 127.0.0.1 (127.0.0.1) port 8080 > GET / HTTP/1.1 > Host: 127.0.0.1:8080 > User-Agent: curl/8.6.0 > Accept: */* > < HTTP/1.1 200 OK < Content-Type: text/html < Content-Length: 228 < Connection: close < <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <script type="module" src="test.js"></script> </head> <body> </body> * Closing connection </html>% [omochi@omochi-mbp swift-react (swift510 *%)]$ curl -v http://127.0.0.1:8080/test.js * Trying 127.0.0.1:8080... * Connected to 127.0.0.1 (127.0.0.1) port 8080 > GET /test.js HTTP/1.1 > Host: 127.0.0.1:8080 > User-Agent: curl/8.6.0 > Accept: */* > < HTTP/1.1 404 Not Found < Connection: close < Content-Length: 0 < * Closing connection Watcher, bundler, and test runner for your SwiftWasm apps - swiftwasm/carton Watcher, bundler, and test runner for your SwiftWasm apps - swiftwasm/carton
Builder.swift がなくなって、それによってStackSanitizerを埋め込む動作がなくなっている？
1 Watcher, bundler, and test runner for your SwiftWasm apps - CI で Swift のインストールにコンテナイメージを使うのをやめて、 tarball からランナーに直接インストールする · swiftwasm/carton@cfc0997
Watcher, bundler, and test runner for your SwiftWasm apps - fix process env · swiftwasm/carton@848ae5a
1
2
1
1
1 1
::0000:0000:0000:0000 とか 0000:0000:0000:0000:0000:0000:: も良いはずだ
Watcher, bundler, and test runner for your SwiftWasm apps - Contributors to swiftwasm/carton
let buildRequestFileHandle = FileHandle(forReadingAtPath: buildRequestPipe)! let buildResponseFileHandle = FileHandle(forWritingAtPath: buildResponsePipe)! while let _ = try buildRequestFileHandle.read(upToCount: 1) { Diagnostics.remark("[Plugin] Received build request") let buildResult = try self.packageManager.build(buildSubset, parameters: parameters) if !buildResult.succeeded { Diagnostics.remark("[Plugin] **Build Failed**") print(buildResult.logText) } else { Diagnostics.remark("[Plugin] **Build Succeeded**") } try buildResponseFileHandle.write(contentsOf: Data([1])) } swift package -v とかswift package -vv でコントロールできるログレベルがあって
Running "/Users/omochi/Library/Developer/Toolchains/swift-wasm-5.10.0-RELEASE.xctoolchain/usr/bin/swift" "package" "--triple" "wasm32-unknown-wasi" "--scratch-path" "/Users/omochi/github/swiftwasm/carton/Tests/Fixtures/SandboxApp/.build/carton" "--disable-sandbox" "-vv" "plugin" "carton-dev" "--pid" "22729" それは出てるよ
info: Running command plugin <PluginTarget: CartonDevPlugin> on package <ResolvedPackage: sandboxapp> with options PluginOptions(_allowWritingToPackageDirectory: false, _additionalAllowedWritableDirectories: [], _allowNetworkConnections: none, _packageIdentity: nil) and arguments ["--pid", "22729"] これは -vv によって出たものかな？ 1
1 Watcher, bundler, and test runner for your SwiftWasm apps - macにsnapshot版のツールチェーンを入れるときは9999問題を回避する作業をする · swiftwasm/carton@b5d38d0
AbsolutePath と RelativePath って、どっちかわからない時はどうすればいいんだ？ 
1
1
div(display: "flex", flex-direction: "column", align-items: "center", gap: "4px") って書ける事だけど 
1
1
FileManager.DirectoryEnumerator の移植の目処も立ちました。 https://github.com/WebAssembly/wasi-libc/pull/522
1
--wasm max-wasm-stack=4194304 ですね． wasmkit-cli run --stack-size 4194304 追加してみました https://github.com/swiftwasm/WasmKit/pull/136path_readlink って readlink とは別なんでしたっけ？もしそうであれば Foundation で readlink しか使われていないからかもしれません． https://github.com/swiftlang/swift-foundation/blob/bc7c25794410715fc7c669ac6b99e0e1868e4510/Sources/FoundationEssentials/FileManager/FileManager%2BSymbolicLinks.swift#L204
path_readlink って readlink とは別なんでしたっけ？もしそうであれば Foundation で readlink しか使われていないからかもしれません． https://github.com/swiftlang/swift-foundation/blob/bc7c25794410715fc7c669ac6b99e0e1868e4510/Sources/FoundationEssentials/FileManager/FileManager%2BSymbolicLinks.swift#L204 readlink実装は最終的に path_readlinkの呼び出しになるはずなんですよね
1
7 3
#if defined(__wasi__) && !defined(_REENTRANT) # define CMARK_THREADING_default 0 #else # define CMARK_THREADING_default 1 #endif #ifndef CMARK_THREADING # define CMARK_THREADING CMARK_THREADING_default #endif #if CMARK_THREADING // thread available #else // no thread #endif #undef CMARK_THREADING #undef CMARK_THREADING_default こんな感じかなと想像してました。 _REENTRANT ってなんだろうと思ったら，wasi-libc の wasm32-wasip1-threads でだけ _REENTRANT が定義されていて，wasm32-wasip1 や wasm32-wasip2 だと定義されていないんですね． https://github.com/WebAssembly/wasi-libc/blob/a05277a6803d99dc5f8d5c250a02cf37ff90882a/expected/wasm32-wasip1-threads/predefined-macros.txt#L2241 1
1
1
1
$ mkdir hoge; cd hoge/ $ docker container run -it --rm -v $PWD:/hoge swift:6.0.2-noble # apt update && apt install --no-install-recommends curl xz-utils binaryen wabt # curl https://wasmtime.dev/install.sh -sSf | bash # source ~/.bashrc # swift sdk install https://github.com/swiftwasm/swift/releases/download/swift-wasm-6.0.2-RELEASE/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle.zip --checksum 6ffedb055cb9956395d9f435d03d53ebe9f6a8d45106b979d1b7f53358e1dcb4 # cd /hoge # swift package init --type executable # swift build -c release --swift-sdk wasm32-unknown-wasi # wasm-opt -Oz -all .build/release/hoge.wasm -o hoge_optimized.wasm -all をつけていたのかを思い出しました．Swift でビルドした Wasm バイナリを wasm-strip してから wasm-opt すると，以前は問題なかったんですが，あるタイミングから wasm-strip の段階で必要な feature が消されちゃうようになったのか wasm-opt の段階で必要な feature が無いみたいな validation エラーが起こるようになったので，何の feature が必要なのかわからなくて -all をつけていたんでした．(私の場合は --enable-bulk-memory --enable-sign-ext だけで十分でした) wasm-strip → wasm-opt してた理由は，wasm-opt 単体や wasm-opt → wasm-strip よりも wasm-strip → wasm-opt の方がバイナリサイズが小さくなる経験則があったからです． なので同じことをしている方がいたらご注意ください． 1
swift-wasi -version -vは以下のようなコマンドラインでswiftを起動してます。 exec swift -target wasm32-unknown-wasi -I -resource-dir /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static -sdk /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk -Xcc -isysroot -Xcc /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk -Xfrontend -tools-directory -Xfrontend /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/bin -static-stdlib -version -v -I -resource-dir となってて-resource-dirがinclude dirとして解釈されちゃってそう
yqはフィールド型で処理分岐とか難しかったから、yqはJSONへの変換だけしてjqにしてフィールド型がarrayだったら〜ってして動く様にした。 あとswift-wasiはswiftcを呼ぶ様にした。 @swift-6.0.3 wasi -emit-assembly -O public func twice(number: Int) -> Int { return number * 2 } .text .file "<swift-imported-modules>" .functype __main_argc_argv (i32, i32) -> (i32)Target: wasm32-unknown-wasi warning: Could not read SDKSettings.json for SDK at: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk
public func twice(number: Int) -> Int { return number * 2 } Target: wasm32-unknown-wasi warning: Could not read SDKSettings.json for SDK at: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk error: link command failed with exit code 1 (use -v to see invocation)
~/Library/org.swift.swiftpm/swift-sdksを/opt/homebrew/share/swift/sdksへのシンボリックリンクに(Homebrewは~以下のディレクトリへ書き込めないため) 2. brew tap-new swiftwasm/swiftwasm 3. /opt/homebrew/Library/Taps/swiftwasm/homebrew-swiftwasm/Formula/swiftwasm-sdk@6.0.rbを以下の内容で作成。 class SwiftwasmSdkAT60 < Formula desc "SwiftWasm SDK 6.0" homepage "https://github.com/swiftwasm/swift" version "6.0.2" url "https://github.com/swiftwasm/swift/releases/download/swift-wasm-#{version}-RELEASE/swift-wasm-#{version}-RELEASE-wasm32-unknown-wasi.artifactbundle.zip" license "" def install prefix.install Dir["*"] sdks_path = share/"swift/sdks" sdks_path.mkpath sdks_path.install_symlink prefix => "#{name}.artifactbundle" end def caveats <<~EOS SwiftWasm SDK #{version} has been installed at: #{prefix} A symlink has been created at: /opt/homebrew/share/swift/sdks/#{name}.artifactbundle EOS end end 4. brew install swiftwasm/swiftwasm/swiftwasm-sdk@6.0 でswift sdk listから認識されるインストールが出来た。 #{version}を使うように変えた
/usr/bin/lldb って apple/swift-lldb なのか 1
sdkRootPath: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk swiftResourcesPath: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static swiftStaticResourcesPath: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static includeSearchPaths: not set librarySearchPaths: not set toolsetPaths: ["/home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/toolset.json"]
print("Hello, WASI!") Target: wasm32-unknown-wasi warning: Could not read SDKSettings.json for SDK at: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.2-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.2-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk error: link command failed with exit code 1 (use -v to see invocation) wasm-ld: error: cannot open /usr/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm32.a: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) 1
print("Hello, WASI!") Target: wasm32-unknown-wasi warning: Could not read SDKSettings.json for SDK at: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0.3-RELEASE-wasm32-unknown-wasi.artifactbundle/6.0.3-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello, world!") // Expectation failed: (greeting → "Hello, world!") == "Hello" } Target: wasm32-unknown-wasi wasm-ld: warning: function signature mismatch: swift_task_escalate >>> defined as (i32, i32, i32, i32) -> void in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(_Concurrency.o) >>> defined as (i32, i32, i32, i32) -> i32 in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(TaskStatus.cpp.o) /usr/bin/swift-swiftc: line 15: 722 Killed wasmtime main "$@"
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello") // Expectation failed: (greeting → "Hello, world!") == "Hello" } ◇ Test run started. ↳ Testing Library Version: 6.2-dev (a7b5435933149b6) ↳ Target Platform: x86_64-unknown-linux-gnu ◇ Test helloWorld() started. ✘ Test helloWorld() recorded an issue at <stdin>:5:3: Expectation failed: (greeting → "Hello, world!") == "Hello" ✘ Test helloWorld() failed after 0.002 seconds with 1 issue. ✘ Test run with 1 test failed after 0.003 seconds with 1 issue.
Target: wasm32-unknown-wasi wasm-ld: warning: function signature mismatch: swift_task_escalate >>> defined as (i32, i32, i32, i32) -> void in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(_Concurrency.o) >>> defined as (i32, i32, i32, i32) -> i32 in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(TaskStatus.cpp.o) /usr/bin/swift-swiftc: line 15: 722 Killed wasmtime main "$@"
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello, world!") // Expectation failed: (greeting → "Hello, world!") == "Hello" } Target: wasm32-unknown-wasi wasm-ld: warning: function signature mismatch: swift_task_escalate >>> defined as (i32, i32, i32, i32) -> void in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(_Concurrency.o) >>> defined as (i32, i32, i32, i32) -> i32 in /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-02-28-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libswift_Concurrency.a(TaskStatus.cpp.o)
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello") // Expectation failed: (greeting → "Hello, world!") == "Hello" } Target: wasm32-unknown-wasi wasm-ld: warning: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-SNAPSHOT-2025-02-21-a-wasm32-unknown-wasi.artifactbundle/6.1-SNAPSHOT-2025-02-21-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libTesting.a: archive member 'Testing.autolink' is neither Wasm object file nor LLVM bitcode
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello, world!") // Expectation failed: (greeting → "Hello, world!") == "Hello" } swift testing -- --event-stream-output-path e.json -
◇ Test run started. ↳ Testing Library Version: 6.2-dev (cabf4d419cf9c8c) ↳ Target Platform: x86_64-unknown-linux-gnu ◇ Test helloWorld() started. ✔ Test helloWorld() passed after 0.001 seconds. ✔ Test run with 1 test passed after 0.003 seconds.
@Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello, world!") // Expectation failed: (greeting → "Hello, world!") == "Hello" } swift testing wasi -- --event-stream-output-path e.json -
Target: wasm32-unknown-wasi ◇ Test run started. ↳ Testing Library Version: 6.2-dev (cabf4d419cf9c8c) ↳ Target Platform: wasm32-unknown-wasi ◇ Test helloWorld() started. ✔ Test helloWorld() passed after 0.095084468 seconds. ✔ Test run with 1 test passed after 0.195883644 seconds.
{ "sdkRootPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk", "swiftResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static", "swiftStaticResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static", "toolsetPaths": [ "/home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi/wasm32-unknown-wasi/toolset.json" ] }--xunit-output は機能して --configuration-path は機能していなさそうであることから，この #if canImport(Foundation) で囲まれた範囲のオプション 3 つが全部無視されてそうに見えました． なので，ツールチェーンか Wasm SDK かわかりませんでしたがそのどっちかのビルドをする時の問題のように思いました． https://github.com/swiftlang/swift-testing/blob/ee700e25f3eb7d51a96ba806413818bbb571b1c8/Sources/Testing/ABI/EntryPoints/EntryPoint.swift#L340-L391 1@inlinable 中の #if は .swiftinterface 出力時に アクティブな領域以外は除去されてしまいます https://github.com/swiftlang/swift/blob/a7b8cb79cd018e7ab54e89dcdb227ca5b21701d8/lib/ASTGen/Sources/ASTGen/CompilerBuildConfiguration.swift#L536-L541 1
atomically: falseでファイル書けたけど、エラーも出てた。 Error: Error Domain=NSCocoaErrorDomain Code=512 "(null)"UserInfo={NSURL=test.txt -- file:///, NSFilePath=test.txt} 2
import Foundation let text="test" do { try text.write(toFile: "test.txt", atomically: false, encoding:.utf8) } catch { print("Error: \(error)") } <unknown>:0: error: compiled module was created by an older version of the compiler; rebuild 'Swift' and try again: /home/bot/.swiftpm/swift-sdks/swift-wasm-DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi.artifactbundle/DEVELOPMENT-SNAPSHOT-2025-03-17-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/Swift.swiftmodule/wasm32-unknown-wasi.swiftmodule
path_readlink をいきなり自分で実装するのはまだハードルが高いなと思ったのでちょうどいいのが来たと思ってやっちゃいました 1
import Foundation let text="test" do { try text.write(toFile: "test.txt", atomically: false, encoding:.utf8) } catch { print("Error: \(error)") } warning: Could not read SDKSettings.json for SDK at: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.0-SNAPSHOT-2025-03-24-a-wasm32-unknown-wasi.artifactbundle/6.0-SNAPSHOT-2025-03-24-a-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk
import Foundation let text="test" do { try text.write(toFile: "test.txt", atomically: false, encoding:.utf8) } catch { print("Error: \(error)") } wasm-ld: warning: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi.artifactbundle/6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/lib_FoundationCollections.a: archive member '_FoundationCollections.autolink' is neither Wasm object file nor LLVM bitcode wasm-ld: warning: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi.artifactbundle/6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libFoundation.a: archive member 'Foundation.autolink' is neither Wasm object file nor LLVM bitcode wasm-ld: warning: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi.artifactbundle/6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libFoundationEssentials.a: archive member 'FoundationEssentials.autolink' is neither Wasm object file nor LLVM bitcode wasm-ld: warning: /home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi.artifactbundle/6.1-SNAPSHOT-2025-03-25-a-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static/wasi/libFoundationInternationalization.a: archive member 'FoundationInternationalization.autolink' is neither Wasm object file nor LLVM bitcode 2
SwiftWasm 6.1 is now available Notable improvements: • No custom patches needed - fully upstreamed • Swift SDK-only distribution • Code coverage support • swift-testing support • VSCode support Check out the release blog post 
https://t.co/ie7ScyKngO
3
2
{ "sdkRootPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-RELEASE-wasm32-unknown-wasi.artifactbundle/6.1-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/WASI.sdk", "swiftResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-RELEASE-wasm32-unknown-wasi.artifactbundle/6.1-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static", "swiftStaticResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-RELEASE-wasm32-unknown-wasi.artifactbundle/6.1-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static", "toolsetPaths": [ "/home/bot/.swiftpm/swift-sdks/swift-wasm-6.1-RELEASE-wasm32-unknown-wasi.artifactbundle/6.1-RELEASE-wasm32-unknown-wasi/wasm32-unknown-wasi/toolset.json" ] }
1
setjmp/longjmp を使った C++ コードが exception を使った Wasm バイナリにコンパイルされちゃうから使わざるを得ないって聞いたことがあります． https://github.com/holzschu/a-shell/discussions/843#discussioncomment-11115672 1
setjmp/longjmp を使った C++ コードが exception を使った Wasm バイナリにコンパイルされちゃうから使わざるを得ないって聞いたことがあります． https://github.com/holzschu/a-shell/discussions/843#discussioncomment-11115672 @cdecl の underscore をはずそうの pitch が出ていて，議論の中で @_expose(wasm) も触れられていますね． https://forums.swift.org/t/pitch-formalize-cdecl/79557 
1
1
wasm-sdk.yml追加とともに変わったぽい。 static_sdk.yml -> static-sdk.yml [https://github.com/swiftlang/swift-org-website/blob/main/_data/builds/swift-6_1-branch/static_sdk.yml] [https://github.com/swiftlang/swift-org-website/blob/main/_data/builds/swift-6_2-branch/static-sdk.yml] static_sdk.ymlが正解ぽくて、apiが動かないというissueもないから、誰も使っていない気がする。 https://github.com/swiftlang/swift-org-website/blob/main/api/v1/install/dev/6.2/static-sdk.json
1
wasm32-unknown-wasip1サポートをボットに追加したら、エラーになる。 @swift-6.2 wasi @swift-6.2 wasip1 -v // HelloEmbedded.swift print("Hello, Embedded Swift 😊") swift wasip1 -v - exit status 1 with stdout:/usr/bin/swift-frontend -frontend -c - -target wasm32-unknown-wasip1 -disable-objc-interop -sdk /home/bot/.swiftpm/swift-sdks/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm.artifactbundle/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm/wasm32-unknown-wasi/WASI.sdk -no-color-diagnostics -Xcc -fno-color-diagnostics -tools-directory /home/bot/.swiftpm/swift-sdks/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm.artifactbundle/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm/wasm32-unknown-wasi/swift.xctoolchain/usr/bin -enable-experimental-feature Embedded -empty-abi-descriptor -resource-dir /home/bot/.swiftpm/swift-sdks/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm.artifactbundle/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-06-17-a_wasm/wasm32-unknown-wasi/swift.xctoolchain/usr/lib/swift_static -use-static-resource-dir -Xcc -D__EMBEDDED_SWIFT__ -no-auto-bridging-header-chaining -module-name main -in-process-plugin-server-path /usr/lib/swift/host/libSwiftInProcPluginServer.so -plugin-path /usr/lib/swift/host/plugins -plugin-path /usr/local/lib/swift/host/plugins -o /tmp/TemporaryDirectory.3xkudn/main-1.oSwift version 6.2-dev (LLVM 5fbc818cf26c90b, Swift 2e1897356956e43) Target: wasm32-unknown-wasip1 <unknown>:0: error: unable to load standard library for target 'wasm32-unknown-wasip1'
#if hasFeature(Embedded) #error("Embedded enabled") #else #error("Full-featured Swift") #endif swift wasi - exit status 1 with stderr:<stdin>:4:8: error: Full-featured Swift 2 | #error("Embedded enabled") 3 | #else 4 | #error("Full-featured Swift") | `- error: Full-featured Swift 5 | #endif 6 |
#if hasFeature(Embedded) #error("Embedded enabled") #else #error("Full-featured Swift") #endif swift wasip1 - exit status 1 with stderr:<stdin>:2:8: error: Embedded enabled 1 | #if hasFeature(Embedded) 2 | #error("Embedded enabled") | `- error: Embedded enabled 3 | #else 4 | #error("Full-featured Swift")
XCTest向けに生成するtest discoveryコードで邪魔してるぽい。 Embeddedでは無理としても、WASIでは動いて欲しいね。 @swift-main testing wasi @swift-main testing wasip1 @Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello") // Expectation failed: (greeting → "Hello, world!") == "Hello" } swift testing wasi -
◇ Test run started. ↳ Testing Library Version: 6.3-dev (b97b57687a8fe60) ↳ Target Platform: wasm32-unknown-wasi ◇ Test helloWorld() started. ✘ Test helloWorld() recorded an issue at <stdin>:4:3: Expectation failed: (greeting → "Hello, world!") == "Hello" ✘ Test helloWorld() failed after 0.033970847 seconds with 1 issue. ✘ Test run with 1 test in 0 suites failed after 0.054957862 seconds with 1 issue.
XCTest向けに生成するtest discoveryコードで邪魔してるぽい。 Embeddedでは無理としても、WASIでは動いて欲しいね。 @swift-main testing wasi @swift-main testing wasip1 @Test func helloWorld() { let greeting = "Hello, world!" #expect(greeting == "Hello") // Expectation failed: (greeting → "Hello, world!") == "Hello" } swift testing wasip1 - exit status 1 with stderr:<stdin>:1:8: error: no such module 'Testing' 1 | import Testing | `- error: no such module 'Testing' 2 | @Test func helloWorld() { 3 | let greeting = "Hello, world!"
1
{ "x86_64-swift-linux-musl": { "swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1": { "toolsetPaths": [ "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/toolset.json" ], "sdkRootPath": "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/musl-1.2.5.sdk/x86_64", "swiftResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/musl-1.2.5.sdk/x86_64/usr/lib/swift_static", "swiftStaticResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/musl-1.2.5.sdk/x86_64/usr/lib/swift_static" } }, "aarch64-swift-linux-musl": { "swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1": { "toolsetPaths": [ "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/toolset.json" ], "sdkRootPath": "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/musl-1.2.5.sdk/aarch64", "swiftResourcesPath": "/home/bot/.swiftpm/swift-sdks/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1.artifactbundle/swift-DEVELOPMENT-SNAPSHOT-2025-06-12-a_static-linux-0.0.1/swift-linux-musl/musl-1.2.5.sdk/aarch64/usr/lib/swift_static", "swiftStaticResourcesPath": "/home/bot/.swiftpm/swift-sd
swift test --swift-sdk wasm32-unknown-wasiもswift test --swift-sdk wasm32-unknown-wasip1もビルドエラーでtest runnerまで辿り着かなかった。 swift test が修正されるっぽいですよ．WasmKit 向けのコマンドラインオプションとかが SwiftPM にハードコーディングされるのはどうなんだろう...って気はしますが． https://github.com/swiftlang/swift-package-manager/pull/9114
1
$は入れない方が良いかと。GitHub上でコードブロック右上のコピーボタンでのコピーに含まれてしまって、貼り付け時に$を削除しないといけない。 $を除去する機能がついたりしてることを、fish-shellのリリースノートで知った。 https://fishshell.com/docs/current/relnotes.html#interactive-improvements一発で理解しきれなかったので後でじっくり読んでみます． ちなみに最後のあたりに書かれていらっしゃる影響範囲の話については，まだ WASI 向けビルドに公式で対応していない swift-format を例に挙げるよりも，XCTest を使ったテストコードとか WASI 対応 済みな swift-syntax とかのビルドが通らないという例の方がインパクト大きく考えて貰えそうだなと感じました． swift-syntax のログもあります． https://github.com/kkebo/swift-syntax/actions/runs/18751650681/job/53492615346 1
