Natasha 
đȘđșEvery developer or dev team can relate -
Previously ITVX
London, UK
| https://twitter.com/SteveBarnegren |
Steve Barnegren
@SteveBarnegren
- 150 Followers
- 369 Following
- 123 Posts
Joe Fabisevich 
@kyle Is this a quote from the Epstein Files?
Cat đđ„ (D.Burch) 
â Dentist: So, do you floss?
Me: Do you use a unique password for every account?
Me: Do you use a unique password for every account?
Marc PalmerOften a designer will just throw in a âuse this icon inline in the textâ requirement into the design. Itâs not unreasonable, but problematic to make it happen.
Except⊠for symbols you can do this easily in SwiftUI with localisation support using string interpolation đ€Ż
Andrew@mattiem Yes, agreed! Implicit behaviours have to be common enough that you learn to mentally âfill in the gapsâ.
(Your comment is making me feel as though I should be using less `@concurrent` though đ - I'll bear that in mind!)
@mattiem Oh, really? What would the purpose be? I've only been doing the whole Swift concurrency thing seriously on a real project for about a week, but I can't envisage when I would use that?
@mattiem I'm not a language designer, but that was also my initial thought!
Swift loves inferring things, so why not here too? If we can boil out some of the 'annotation clutterâ that would probably be a good thing?
Marking a function as `async` and `@concurrent` feels somewhat `@redundant`.
ChatGPT is so two-faced. I can literally see the snark in the reasoning.
"The user must be inexperienced in X and is obviously confused..."
Then it comes back with something like "That's an astute observation!"