swift VS swift-corelibs-foundation

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

a : https://github.com/apple/swift-corelibs-foundation/blob/main...

I wouldn't want to be the guy relying on this table advancement for this project. The fact that they're rewriting it in pure swift probably says a lot about the quality of the current approach.

b: makes absolutely no difference from a developer perspective. if you want to run threads in swift you're going to use gcd.

c: my take with all apple software tech has been to wait until they've dogfooded their own tech long enough to make it useable. Worked very well for me so far, thank you very much.

Correction: rewrite of PARTS of Foundation

There already was an open-source project to rewrite ALL of foundation, but it had stalled on the shores of having to re-implement everything:

  https://github.com/apple/swift-corelibs-foundation

The (shitty) old Linux implementation has been on GitHub for years.

Sigh... The traditional argument is that every dependency is of the same quality and trustworthiness of the language Standard Library.

If I use the SL, then I should also have no problem using some lashed-up chimera that has a dependency hierarchy that spans three continents.

Like I said, I'll do things my way.

For the record, here's a peek at some of the "worthless" packages that I use in my own work: https://github.com/RiftValleySoftware

Also, for the record, here's the Swift Foundation Library: https://github.com/apple/swift-corelibs-foundation

It has plenty of open issues: https://github.com/apple/swift-corelibs-foundation/issues

If every dependency chain can match these, yhen I'll be open to considering them.

As it is, I do use the occasional external package, but I'm picky.

CoreFoundation is (partially?) open-source and cross-platform now: https://github.com/apple/swift-corelibs-foundation

Partly this is doable because although RFC 2616 specifies a max URL length of 2048 bytes, most browsers allow much longer, with Chrome and Firefox allowing at least 64k chars (that's what they'll display but it seems like more is happily processed), while Safari allows URL strings up to 2GB in size[1]!

[1] https://github.com/apple/swift-corelibs-foundation/blob/b23d...

Regarding your point #3, Swift does indeed have an open-source cross-platform implementation of Foundation. swift-corelibs-foundation

Foundation is open source and (mostly) works on Linux. What else do you want to see “opened up?”

Foundation is not the standard library of Swift. Swift has its own standard library that is bundled with the language on all platforms that are supported.

And Foundation itself isn't written in Swift, a good portion is written in C.

> A significant portion of the implementation of Foundation on Apple platforms is provided by another framework called CoreFoundation (a.k.a. CF). CF is written primarily in C and is very portable. Therefore we have chosen to use it for the internal implementation of Swift Foundation where possible. As CF is present on all platforms, we can use it to provide a common implementation everywhere.

https://github.com/apple/swift-corelibs-foundation/blob/main...