SaaSHub helps you find the best software and product alternatives Learn more →
Swift-evolution Alternatives
Similar projects and alternatives to swift-evolution
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
RegExr
RegExr is a HTML/JS based tool for creating, testing, and learning about Regular Expressions.
-
-
-
-
-
-
-
-
RE2
RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
-
-
-
-
swift-corelibs-foundation
The Foundation Project, providing core utilities, internationalization, and OS independence
-
-
-
-
compose-multiplatform
Compose Multiplatform, a modern UI framework for Kotlin that makes building performant and beautiful user interfaces easy and enjoyable.
-
-
swift-evolution discussion
swift-evolution reviews and mentions
- A Vision for Embedded Swift
- Swift: Precise Control Flags over Compiler Warnings
-
Prioritize Work at the Task Level
More reading about how the Swift Task API utilizes and propagates QoS is in the proposal doc.
https://github.com/swiftlang/swift-evolution/blob/main/propo...
-
Swift 6
I think your link got cut off. Here’s the direct link to the section on when to use typed throws. I hadn’t read this before, and it changes how I’ll approach them. Thanks for pointing it out!
https://github.com/swiftlang/swift-evolution/blob/main/propo...
- Integer Generic Parameters
- Objective-C Implementations in Swift
-
Swift's native Clocks are inefficient
According to their changelog[0], Clock was added to the standard library with Swift 5.7, which shipped in 2022, at the same time as iOS 16. It looks like static linking by default was approved[1] but development stalled[2].
I expect that it's as simple as that: It's supported on iOS 16+ because it's dynamically linked by default, against a system-wide version of the standard library. You can probably try to statically link newer versions on old OS versions, or maybe ship a newer version of the standard library and dynamically link against that, but I have no idea how well those paths are supported.
0. https://github.com/apple/swift/blob/main/CHANGELOG.md
1. https://github.com/apple/swift-evolution/blob/main/proposals...
2. https://github.com/apple/swift-package-manager/pull/3905
-
Byte-Sized Swift: Building Tiny Games for the Playdate
[A Vision for Embedded Swift](https://github.com/apple/swift-evolution/blob/main/visions/e...) has the details on this new build mode and is quite interesting.
> Effectively, there will be two bottom layers of Swift, and the lower one, “non-allocating” Embedded Swift, will necessarily be a more restricted compilation mode (e.g. classes will be disallowed as they fundamentally require heap allocations) and likely to be used only in very specialized use cases. “Allocating” Embedded Swift should allow classes and other language facilities that rely on the heap (e.g. indirect enums).
Also, this seems to maybe hint at the Swift runtime eventually being reimplemented in non-allocating Embedded Swift rather than the C++ (?) that it uses now:
> The Swift runtime APIs will be provided as an implementation that’s optimized for small codesize and will be available as a static library in the toolchain for common CPU architectures. Interestingly, it’s possible to write that implementation in “non-allocating” Baremetal Swift.
-
Borrow Checking Without Lifetimes
I may be out of my depth here as I've only casually used Rust, but this seems similar to Swift's proposed lifetime dependencies[1]. They're not in the type system formally so maybe they're closer to poloneius work
[1]: https://github.com/apple/swift-evolution/blob/3055becc53a3c3...
-
A note from our sponsor - SaaSHub
www.saashub.com | 18 Jan 2025
Stats
swiftlang/swift-evolution is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of swift-evolution is Markdown.
Popular Comparisons
- swift-evolution VS compose-multiplatform
- swift-evolution VS kotlinx-datetime
- swift-evolution VS foundationdb
- swift-evolution VS PeopleInSpace
- swift-evolution VS okio
- swift-evolution VS swift
- swift-evolution VS kotlin-wrappers
- swift-evolution VS swift-algorithms
- swift-evolution VS kotlindl
- swift-evolution VS KEEP