swift-parsing VS swift

No idea about parsing and evaluating in the same library, but there’s an excellent parser library from PointFree.

Sorry about that, broken links have been fixed in the episode and here's a link to the library: https://github.com/pointfreeco/swift-parsing.

If you want to do parsing, I strongly recommend Point-Free's Parsing library!

Honestly I still have a difficult time understanding Regex’s, and maintaining them can be hard since once small change can completely change how the Regex works. I would instead opt for a real parsing library, like for instance PointFree’s swift-parsing, who’s clear and idiomatic API makes it easy to understand what’s really going on. It’s also very, very performant - almost as performant as making a custom hand-rolled parser.

Personally, I would pull out my parser library and use that (the documentation is lacking, so if you're just starting out it can be hard to figure out what's going on, but you could use Point Free's parser library to do it like so:

I’m currently using the composable architecture. TCA is the result of video series by Point Free that discusses what Apple provides with SwiftUI, in detail, and iterates though the of the evolution of the architecture, to fill in the gaps. Most of the content is available by subscription, but there is free content as well, which includes a four part overview on the architecture itself. I highly recommend subscribing as the detailed walkthrough of building the architecture is extremely useful and helps clarify some of the more complicated aspects of its use.

https://github.com/apple/swift/pull/73429

This algorithm produces biased result with probability 1/2^(32-bitwidth(N)). Using 64 or 128 random bits can make the bias practically undetectable. Comprehensive overview of the approach can be found here: https://github.com/apple/swift/pull/39143

Because of C/C++ interop, and integration with CMake, you can just add Swift to a Zephyr project and it pretty much Just Works. [The docs](https://github.com/apple/swift/blob/main/docs/EmbeddedSwift/...) should mostly apply to the Zephyr SDK as well.

Fortunately, the Observation framework is part of the Swift 5.9 standard library. We can learn more information by examining its source code.

They do! See https://github.com/apple/swift/blob/main/docs/LibraryEvoluti...

You can also see an example of what a different high level language integration with Swift ABI looks like here: https://github.com/dotnet/designs/blob/main/proposed/swift-i...

So is differentiable Swift a package for Swift or is it part of the Swift standard library? The video says go to swift.org but I can't find any info about differentiable Swift on that site.

Swift's Differentiable Programming Manifesto. Swift has a powerful differentiable programming component, integrated with the compiler.

You can do the same thing the other way around - https://github.com/apple/swift/blob/main/docs/Android.md.

Codable (along with other derived conformances like Equatable, Hashable, and RawRepresentable) is indeed built in to the compiler[0], but unlike Serde, it operates during type-checking on a fully-constructed AST (with access to type information), manipulating the AST to insert code. Because it operates at a later stage of compilation and at a much higher level (with access to type information), the work necessary is significantly less.

With ongoing work for Swift macros, it may eventually be possible to rip this code out of the compiler and rewrite it as a macro, though it would need to be a semantic macro[1] rather a syntactic one, which isn't currently possible in Swift[2].

[0] https://github.com/apple/swift/blob/main/lib/Sema/DerivedCon...