A rich evil white dude getting found guilty of a felony and his “punishment” is literally nothing, legally-defined nothing, instead he … just gets to become president — this is Peak America.
=> More informations about this toot | View the thread
tfwu know that some public API surface has the wrong combination of @-MainActor and/or @-Sendable on some block parameter and you'd bet money it's because nobody outside the language maintainers (and a handful of 3rd-party nerds) are following the concurrency evolution closely enough to give a crap about it so now it’s up to you, dear third-party developer, to annotate dozens or hundreds of call-sites with MainActor.assumeIsolated because the platform library owners don't have the guts to do it.
=> More informations about this toot | View the thread
I'm glad ChatGPT exists if only to help me resolve my word-finding difficulties that seem to get worse all the time.
Today's example: “the calculus”.
Couldn't think of it, kept getting stuck on “the circumstances” or "the reckoning”.
=> More informations about this toot | View the thread
@mattiem @cocoaphony I've added a big update (the second half) to my post from yesterday, inspired by ya’ll's feedback: https://jaredsinclair.com/2024/11/12/beware-unchecked.html
TL;DR I went down the rabbit hole of ~Copyable (noncopyable) as it's used by Mutex and learned some helpful things I'm going to put into backportable Mutex alternatives.
=> More informations about this toot | View the thread
Beware @-unchecked Sendable, or Watch Out for Counterintuitive Implicit Actor-Isolation
Swift 6 puts runtime assertions on your code that are not possible to remove without refactoring to address compile-time issues, so you better hope you have write-access to the code in question.
https://jaredsinclair.com/2024/11/12/beware-unchecked.html
=> More informations about this toot | View the thread
@isaiah Help me remember something. I remember reading, or being told, that there were specific reasons to avoid, in Objective-C, providing a property named exactly id
. Like, besides the way it creates human confusion as an exact match for the reserved keyword id
, there was some reason (or reasons) beyond that which made it inadvisable to do so. I cannot recall the specific reasons anymore, and Google absolutely fails to find my answers. Can you recall what the specific reasons were?
=> More informations about this toot | View the thread
I don't remember writing this but I still dig it.
=> More informations about this toot | View the thread
=> More informations about this toot | View the thread
No matter how hard I try I am not getting better at this barista art thing.
=> More informations about this toot | View the thread
Unable to install to an iPhone 16 Pro Max (Developer mode enabled, powered on, connected, unlocked) using Xcode 16's final release build (16A242d).
Anyone else seeing this?
=> More informations about this toot | View the thread
@mattiem @cocoaphony The error disappears with (among other possible workarounds) prefixing the CoreData import with @-preconcurrency, however that feels like a cop-out. What's your gut take here: are we (Apple platform devs generally) facing a medium-term future where there are lots of valid "correct” API usages that, because they cannot be checked as valid and correct by the Swift concurrency checker, will permanently require manually suppressing and working around these warnings and errors?
=> More informations about this toot | View the thread
@mattiem and @cocoaphony I'm curious what ya'll think about this. So my teammates and I were hoping that by Xcode 16 RC there would be better support for concurrency when working with CoreData. That hasn't happened, and doesn't feel like it's ever going to happen. Problem: we want to be ready to opt into Swift 6, and we want to avoid having to jump through hoops to quell warnings and errors. But then we run into stuff like this all over the place: (1 of N)
=> More informations about this toot | View the thread
I missed the "buildable folders" feature from the Xcode 16 release notes. This is going to be really helpful—avoiding the most common cause of merge conflicts—just need to manually apply it to existing projects.
=> More informations about this toot | View the thread
Remember when writing Swift wasn't just about satisfying the Swift Compiler?
=> More informations about this toot | View the thread
My name is Blue Canary, one note spelled L-I-T-E. . . .
=> More informations about this toot | View the thread
What if getting shot at softens him? for reasons that are personal and idiosyncratic, hard for outsiders and media analysts to quantify or rationalize? A manifestation of whatever deeper quirk or trait causes his germophobia, his self-destructive tendencies.
=> More informations about this toot | View the thread
[BLOG POST] Bookmarking Xcode Project Search Results:
https://jaredsinclair.com/2024/07/12/bookmark-search-queries.html
This hard-to-find feature has turned out to be something I use all day long.
Hat tip to @jaminguy
=> More informations about this toot | View the thread
@holly Howdy, found an edge case in Xcode 16 Beta 3 related to TaskGroup under Swift 6 language mode, filed as FB14253266.
The waitForAll()
isolation inference fails with the regionbasedisolation_unknown_pattern diagnostic when called on a TaskGroup created within an actor-isolated method:
I'm sorry to bother you here, but my team is trying to determine whether this is a transitory issue, or whether we need to stop using TaskGroups with Actors and rearchitect some stuff. Thanks!
=> More informations about this toot | View the thread
This post by Charity Majors (@mipsytipsy) contains both (1) the most lifelike description of being on a software development team I’ve ever read and (2) a clarion call that we all need to echo at work, everywhere, all the time, because if we don’t, we’re gonna eat our young.
https://stackoverflow.blog/2024/06/10/generative-ai-is-not-going-to-build-your-engineering-team-for-you/
=> More informations about this toot | View the thread
BLOG POST: How Do You Know Whether or Not SwiftUI Previews and Preview Content Are Excluded From App Store Builds?
https://jaredsinclair.com/2024/05/20/preview-content.html
Been bit by this so many times I finally spent some time in Hopper, decompiling sample projects until I fully understood what's going on under the hood.
=> More informations about this toot | View the thread
=> This profile with reblog | Go to jaredsinclair@mastodon.social account This content has been proxied by September (ba2dc).Proxy Information
text/gemini