swift-win32 VS swift

For jumping abord, there are not very many frameworks for UI development. There is https://github.com/compnerd/swift-win32 which is less WinForms and more Common Control based. There were a couple of different attempts for WinRT to get XAML based UI systems. There was no official support for UWP, and that would likely require some tweaks to the runtime.

Even Microsoft has someone dedicating their time to building Win32 support.

Swift does run on windows now. There’s also a package that lets you use Win32 to write GUI apps (https://github.com/compnerd/swift-win32). The core code (data models, networking, etc) can be common, but UI will have to be different (Win32 on windows and AppKit/Catalyst/SwiftUI on Mac)

As others have mentioned, UIKit is an Apple framework and not available on Windows, though you should be able to use the Win32 APIs to build out UI interfaces. Alternatively, you can experiment with https://github.com/compnerd/swift-win32 for a nice layer on top which abstracts out some of the details of the Win32 API. Unfortunately, that is not as fleshed out as one would like to build complex applications, but that is something which more usage and work on library should be able to resolve.

For native apps, there's this, which gives an AppKit-like interface to build GUIs.

If you’re looking for Windows first projects with Swift, https://github.com/compnerd/swift-win32 is pretty cool.

Also check out this project by a member of the Swift core team, which is a set of bindings for the Win32 API for Swift on Windows.

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...

`Int` is a regular struct with a single stored property of type `Builtin.Word` . But the latter is a magical compiler built-in. Source for integer types is generated from this template - https://github.com/apple/swift/blob/9da65ca0a15fdf341649c994b0a77ec3b71f2687/stdlib/public/core/IntegerTypes.swift.gyb