I’m looking for resources to teach Swift concurrency in Swift 6 to other engineers. Ideally similar to the objc io swift concurrency book.
Particularly interested in strategies to avoid unstructured concurrency and Mutexes, since that’s the stumbling blocks I’ve seen most.
Are recycled materials universally bad? Outerknown is expensive relative to American Eagle and seems very proud of recycling various materials; cashmere, cotton, “fibers from landfills”
Big crypto vibes from the recent narrative that if you don’t “keep up with AI tools” you’ll be “left behind.”
If you make an ABI, but don’t document it, do you actually have an ABI?
Asking for a friend who is a multi billion dollar company
is fulton county okay?
eekum bokum
I for one will be spelling this `[Int twitter 5]`
forums.swift.org/t/pitch-inli...
My favorite swift language bug: stored properties whose storage takes up zero bytes have the same hash and are equal to other adjacent properties
Contributing to the swift compiler is a pretty big deal even for a senior+ iOS dev though… I imagine “my work was accepted by Apple into arguably their most important open source project” does wonders at a college job fair
There’s at least two up right now that seem AI generated to me, down to the author of one of them responding with “sorry for the confusion” followed by another wall of text. Both from people who want to do GSoC.
Honestly I really envy the patience of the guy who responded
Apropos of nothing, the swift forums really needs a policy requiring that any use of AI to generate pitches be disclosed
I broke withTaskExecutorPreference
forums.swift.org/t/equivalent...
Seems like @ MainActor in Swift does different stuff at runtime than using an `isolated` parameter for a function called on MainActor. On a related note, testing unstructured concurrency is really hard
If Atlassian can afford an F1 title sponsorship they can afford to make updating a jira ticket faster than an F1 pitstop (2-3 seconds)
I want to see the author of this story investigate the New York Times’ own insistence on injecting the words “curbed” and “freewheeling” into as many articles as possible
Until the last homeless person in San Francisco is either housed or institutionalized, as appropriate, I don’t want to hear about a single California public servant’s podcast. I especially don’t want to hear their opinions about sports
Body macros 🤝 typed throws
crashing the compiler
Not sure if I know where to route it but I’ll see what I can do. Just curious, are the vouchers part of some corporate business program at your employer or is this like “I took my car for repairs and they gave me a voucher” one off kind of a deal?
The funniest thing about the Zelensky half zip scandal is how shabbily Trump and a lot of the other conservative figures who are upset dress. Yet another of these “every accusation is a confession” things; clearly none of them enjoy the performance of wearing off the rack brioni suits or whatever
Imo ukraine has given America the best deal since the Louisiana purchase: we spent trillions of dollars on defense specifically to counter Russia over the past fifty or so years, and they’re grinding the Russian army into powder for a measly hundred billion or so.
list of things that have SEs approved, have not shipped, that i really need:
- static member key paths
- accessor macro on lets
- body macro on computed vars
- abi annotation (for crimes)
Tired: update xcode, your UI snapshots have all failed
Wired: update swift syntax, your macro unit tests have all failed
some people make Type Systems, i make Type Sins
Imagine being Microsoft, spending billions on AI, and not bringing back clippy
do we really need ethics experts for this though
come on
we’ve seen this movie before and it ends with the entire country cutting up curtains to make masks while the dipshit capers on tv asking if drinking bleach will help
My WWDC prediction: apple will announce a core data replacement which leverages the new macro system to rewrite predicates as SQL queries, and the type wrapper annotation to duplicate existing core data behaviors.
