undefined | Better HN

0 pointsrefulgentis11mo ago0 comments

Amazing!

Why are they framing it as a proposal if it's done? (if this comes across as Socratic, it is unintentional, I genuinely don't understand why the author would be posting a proposal when it is done)

EDIT: My naive reading of https://github.com/swiftwasm/swift/issues is there's a lot, lot, to go. TL;DR: open from 2021, stdio FILE not available in WASILibc. Long version, filed in 2020 and open: "Pointers needed on WASILibc", "Make the toolchain work without Xcode installed", "Enable libdispatch or provide stubs for it", 2022 "canImport(Dispatch) is wrongly truthy on WASI target", "wasm lacks signal support" (broke/regression in Sept. 2024, still open)

0 comments

jagged-chisel11mo ago

> "Make the toolchain work without Xcode installed”

On macOS. Works fine on Linux.

This is such an easy ask. The only thing holding it back, imo, is Apple. Can’t let the plebs bypass Xcode to develop on their Macs!

My workaround is running a container with Linux Swift installed. Of course, I’m not targeting an Apple OS so I have the flexibility.

Someone11mo ago

> Can’t let the plebs bypass Xcode to develop on their Macs!

AFAIK, they support that. https://www.swift.org/swiftly/documentation/swiftly/getting-...:

“Overview

To get started with swiftly you can download it from swift.org, and extract the package.

On macOS you can either run the pkg installer from the command-line like this or just run the package by double-clicking on it (not recommended):

    installer -pkg swift-x.y.z.pkg -target CurrentUserHomeDirectory

Now run swiftly init to finish the installation:
~/usr/local/bin/swiftly init
Swiftly will install itself and download the latest available Swift toolchain.”

j / k navigate · click thread line to collapse