Florian

@ffried
153 Followers
266 Following
505 Posts
CTO/CIO and senior #iOS and #macOS developer using #Swift @ ser.soft GmbH (sersoft.de).
Bloghttps://ffried.codes
GitHubhttps://github.com/ffried
Workhttps://sersoft.de
Show threadFlorianDec 17
@jensimmons Just got my hands on a machine running Safari 26.1, where _all_ cursors work.
Gist is also updated.
FlorianDec 17
@jensimmons Is there a list somewhere of what cursors Safari / WebKit (not sure who's to blame here) ought to support?
I’ve noticed that between Safari 26.0.1 and 26.2, a lot of cursors seem to have gone missing, and I'm not sure if this is a bug.
HTML file for this is here: https://gist.github.com/ffried/8446e04fc33d414ca74885b616799f72
FlorianNov 14
At this point, I’m assuming Apple just fired their whole design QA team.
Show threadFlorianSep 22, 2025
Doesn't look like Apple wants any feedback on current Xcode versions either.
FlorianSep 22, 2025

You better not enable the `.treatAllWarnings(as: .error)` SwiftSetting in your packages if you want to use said package as a dependency in another project/package that you edit in Xcode…
Apparently, Xcode inserts `-suppress-warnings` automatically for dependencies, but opts not to remove the `-warnings-as-errors` option.

Note that the issue isn't with suppressing warnings for dependencies itself. SwiftPM does so as well: https://forums.swift.org/t/conflicting-options-wwarning-and-suppress-warnings/76714/3.

FlorianSep 24, 2024

For the #Swift (and possibly #Vapor) folks:
I think I found a mis-compile in Swift 6. Using ConsoleKitTerminal's LoggerFragments seems to lead to missing witness tables...

Am I missing something or should I report this?

FlorianSep 23, 2024

Any ideas how this could work in #Swift 6?
Element is a generic parameter that might or might not be Sendable. In either way, I'd argue that this should be safe (at least from a concurrency perspective).

/cc @mattiem

Show threadFlorianSep 23, 2024

Turns out that this is due to Xcode 16 using debug builds for previews as well, thus erasing `some` return types to their `@ _typeEraser` type (if any).

Thanks @joe for providing this insight and finding the build setting to turn this off: https://f.duriansoftware.com/@joe/113170928606701687

However, I haven't found a way to disable it in SPM. But for #SwiftUI, I simply “opened up" the `AnyView` wrapper using `Mirror`.

Joe Groff (@[email protected])

@[email protected] Yeah, previews and debug builds now share build products, so views in debug builds get the AnyView wrapping. You can set SWIFT_ENABLE_OPAQUE_TYPE_ERASURE=NO in the build settings to disable this separately (though this probably breaks previews, so you might want to set up a separate scheme if you use previews)

Durian Software
FlorianSep 20, 2024
Does anyone know why #swift 6 erases `some View` to `AnyView`?
FlorianSep 9, 2024

So, just so I get this right: the new #swift_testing is actually bundled in Xcode (16) but not Swift (6)..?

As in: maintaining cross-platform #Swift packages just got worse, since they need an extra dependency on Linux but not on Darwin?
Who thought that would be a good idea?