Swift is exploring a cute idea for library transparency: you can distinguish between "this ABI is guaranteed to keep working" and "I want an extra layer of indirection so I can add to data structures without breaking downstream users".
https://forums.swift.org/t/pitch-library-evolution-for-stable-abis/23026
miniblog.
Related Posts
I've released difftastic 0.68! A smaller update, but still worth upgrading:
* Improved Bash, C, Go, Lua, Nix, Perl, Python, Rust, Scala, Swift and YAML parsing.
* Minor display and git compatibility fixes.
Just released a new version of difftastic!
* Verilog support
* Improved Erlang, F#, Gleam, Pascal and Swift
* Better detection of binary files
I'm a huge fan of Swift's 'Error Handling Rationale' design document: https://github.com/swiftlang/swift/blob/9315673c003875158852579bd1f33480cdec5461/docs/ErrorHandlingRationale.md#fundamentals
It carefully defines terminology and compares with other languages, so you can understand Swift's position and preference in the design space.

