swift-numerics
swift-evolution
Our great sponsors
swift-numerics | swift-evolution | |
---|---|---|
5 | 124 | |
1,619 | 15,003 | |
1.1% | 0.8% | |
5.1 | 9.7 | |
5 days ago | 6 days ago | |
Swift | Markdown | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
swift-numerics
-
Modules in Swift Playgrounds
You'll need to install the Swift Package. If you're on iPad, just press the Add File → Package buttons and then there should be a text box. Then just paste in the URL: https://github.com/apple/swift-numerics
-
How do I write a math function that uses addition and division and is generic across number types like Int and Double?
I don’t know if it applies, but you could try checking out the Numerics package?
-
Are people using Swift for machine learning / differentiable programming outside of Apple?
Apple released a numerics library under Apache 2! This is great news.
-
Does anyone know if Swift's version of Penrose tiling algorithm exists somewhere?
I implemented a Swift version here for fun! The core logic is strictly similar to https://preshing.com/20110831/penrose-tiling-explained/. I used the great Swift Numerics Package for complex numbers. I also added UI logic with SwiftUI to visualize and experiment.
-
The New Open Source Package Swift Algorithims is Finally here
Packages like Swift Algorithms (and Swift Numerics) complement the Swift Evolution process by providing a means to:
swift-evolution
-
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...
-
Functional Ownership Through Fractional Uniqueness
Swift recently adopted a region-based approach for safe concurrency that builds on Milano et al’s ideas: https://github.com/apple/swift-evolution/blob/main/proposals...
- Swift-evolution/proposals/0373-vars-without-limits-in-result-builders.md
- The Swift proposal that removed the ++ and –- operators (2017)
-
Crafting Self-Evident Code with D
No, it's not. Refcounting CAN be a garbage collection algorithm, but in Swift it's deterministic and done at compile time. Not to mention recently added support for non-copyable types that enforces unique ownership: https://github.com/apple/swift-evolution/blob/main/proposals...
- Statically link Swift runtime libraries by default on supported platforms
- (5.9) What is the point of a SerialExecutor that can silently re-order jobs?
-
Mac shipments grow 10%, as all major PC brands see downturns.
You can stackallocate buffers with unsafe Swift but it's not exactly fun to use. https://github.com/apple/swift-evolution/blob/main/proposals/0322-temporary-buffers.md
-
Can someone explain how Task really works in terms of threads (I couldnt ask all the questions with the swift team today)?
If the docs do not suffice, read the concurrency proposals of Swift Evolution. The authors describe the semantics in a very detailed way there.