swift

relatively quiet because there's a lot of behind-the-scenes work extending the initial blush of lifetime controls to iterators, stdlib types, etc. (never mind parameter packs). They're in year 4+ of building out the function-coloring of concurrency and isolation domains (6.2 had an "easy" mode that caused lots of problems), so adding year 2+ dataflow coloring of lifetimes is doubly complicating. Naturally, diverse support for exciting new features results in quite a spread in the third-party library ecosystem of support for various language features. And now with AI entrepreneurs rewriting and porting any project that can score hits and kudos, the usual open-source authorities are losing their steam. Finally, there's the baseline platform complexity of multiple OS and devices, physical and simulator debugging support, cloud CI... So: that makes four dimensions of complexity. As a Swift developer you'd have to be very careful to stay on a working path as things shift underneath you. All for the love of it?

ttps://download.swift.org/swiftly/linux/swiftly-$(uname -m).tar.gz && \ tar zxf swiftly-$(uname -m).tar.gz && \ ./swiftly init --quiet-shell-followup && \ . "${SWIFTLY_HOME_DIR:-$HOME/.local/share/swiftly}/env.sh" && \ hash -r But, god damn, the size is huge, Unsupported Linux platform Debian GNU/Linux 13 (trixie) is not an officially supported platform, but the toolchains for another platform may still work on it. Please select the platform to use for toolchain downloads: 0) Cancel 1) Ubuntu 24.04 2) Ubuntu 22.04 3) Ubuntu 20.04 4) Ubuntu 18.04 5) Fedora Linux 39 6) RHEL 9 7) Amazon Linux 2 8) Debian GNU/Linux 12 Pick one of the available selections [0-8] : 8 Installing swiftly in /home/debby/.local/share/swiftly/bin/swiftly... Creating shell environment file for the user... Updating profile... Fetching the latest stable Swift release... Installing Swift 6.2.3 Downloading Swift 6.2.3 100% [========================================================] Downloaded 947.6 MiB of 947.6 MiB Verifying toolchain signature... Extracting toolchain... The file `/home/debby/ent/agateteper/.swift-version` has been set to `Swift 6.2.3` The global default toolchain has been set to `Swift 6.2.3` Swift 6.2.3 is installed successfully! There are some dependencies that should be installed before using this toolchain. You can run the following script as the system administrator (e.g. root) to prepare your system: apt-get -y install libicu-dev libcurl4-openssl-dev libedit-dev libsqlite3-dev libncurses-dev libpython3-dev libxml2-dev pkg-config uuid-dev libstdc++-12-dev 947.6 MiB ! I wonder why is that...

https://github.com/swiftlang/swift/blob/256ff127c93d7e59a75f... I'm not sure what the parent commenter meant when they claimed that "Result <e, t> of yours is a Result (e, t) in Haskell." In Haskell, `(e, t)` would be the pair type (the binary product type).

tantly. Both PageSpeed Insights and Pingdom rate my site's performance as Excellent. It's server side rendered, so it works even with JavaScript disabled (though enabling it gives you a few extra features like quick access to archive.org for each link). Kind of works even with CSS disabled. The site doesn't have any ads (I hate them and have installed ad-blockers everywhere!), no trackers, or analytics. CloudFlare automatically enables Real User Monitoring (RUM) on sites. The very first thing I did was disable this thing. I am self-hosting the site on an old Mac mini. It's a 2020 Intel model which has a 2018 chip (Intel's 3 GHz 6-core Core i5) and 32gb ram. Qwen model takes about 5.5GB of ram usage and does my headline classification in about 2 seconds each. The Swift app talks to a locally running Qwen3 8b LLM for classifying whether a headline is political or not. This is done over a REST API by Ollama. This seems to work pretty well and far better than Apple's Foundation Models. Originally, I tried using Apple's Foundation Models for this classification. When it worked, it worked decently well. However, many headlines (and even pretty bland headlines) would somehow trigger its guardrails. I asked Stack Overflow for help on this but as usual, they closed the question for lack of details: https://stackoverflow.com/questions/79785822/how-to-disable-... For example, this headline: > SEC approves Texas Stock Exchange, first new US integrated exchange in decades Would hits the Apple's guardrails and throw an error saying `refusal: May contain sensitive content`. Apple does provide a "permissive guardrail mode" as per: https://developer.apple.com/documentation/foundationmodels/i... This does end up allowing some texts to work. However, it still failed for some other ones. That's when I gave up on using Apple's foundation models and switched to the Qwen3 8b model which had no such issues. It's pretty sad how the Foundation Models have so much potential but Apple has severely neutered them. I originally tried the apple foundation models on my newer mac with m4 chip and once I had the issue with their guardrails, I decided to just switch to Qwen model which runs on Intel and used my old Mac mini for it. An issue I ran into was that my Swift app was intermittently crashing. Root cause were two issues: 1. First one had to do with accessing the SQLite database from multiple threads. Apparently, for multi-threading use, SQLite needed to be initialized with a `SQLITE_OPEN_FULLMUTEX` flag. 2. Second one was a "Bad file descriptor" error from the macOS operating system itself. Had to do with a possible bug in Process.run() which would cause it to crash after some time: https://github.com/swiftlang/swift/issues/57827 Was able to fix it using the above workaround/solution of "fileHandleForReading.close()". Lets see how long the site stays alive now without crashing :) Feel free to ask questions.