@chockenberry@Gte You could maybe write a macro that adds public to every field unless it’s already got an access control modifier. Likely overkill, but it would give you the behaviour you want!
Ack, can’t find it now, but does anyone have the link for that Swift init vs. type name for initialisation thread that was on the Swift forums? #iosdev
@Cyberbeni Yeah, I remember there was a thread recently on the Swift forums where some people tried actively working out exactly what combo of type name, type decl., and/or init produced the shortest compile times.
@gernot absolutely! I wouldn’t use something else, because xcodeproj is a horrible format and I don’t want to deal with the git conflicts. And I like the enforced separation that SPM gives modules.
I’m intrigued to see what happens with Tuist, though… I think it does go or is going beyond project generation.
@gernot lol, yeah, I've not seen on-device previews work for yeaaaaars.
It's just sad, because the theory of SPM (and, in some places, the practice) as a means of project structure is soooooo much better than the alternative. But then you hit a sharp edge, and it's horrible.
@gernot Specifically regarding previews, is that possibly because you didn't have that scheme selected in Xcode? This is the only way I get Previews working with SPM:
Module is defined as both a target and a product.
Scheme in Xcode (from products) is the one you want to preview
The files currently visible in an editor are only from that given module. Somehow, hiding those editors is good enough too.
In Xcode 15.4, SPM now auto-generates Swift symbols for catalog assets.
That's great! Except they're declared internal, therefore they're useless in a package whose sole purpose is defining a Design System 😕
@harshil@mergesort Definitely necessary for anything other than the most obvious Array assignments. Also useful if you use static methods/are storing enum cases.
@xtaldave I think this is huuuugely overstated. He trained his own local LLM on his own artwork to achieve the particular psychedelic effect he wanted. There's no "stealing" from other artists here. It's just using a new tool for a particular purpose. The fact he didn't animate each (key)frame to get there doesn't mean it's fake or not worthy, IMO.
@b3ll I wonder if they will ever give in and just make the rules global? Or will it take literally every country/trading bloc to force them to?
Like, if the EU, U.S., UK, Japan, South Korea etc. force these changes, will they make them global, or do you think they’ll still hold out in India, China, etc. Is there any threshold until they just make it universal? At this point, I wouldn’t be surprised if they hold on wherever they can, no matter how small the market.
git bisect is one of the most useful tools in any developer’s arsenal. Spent a few hours tweaking code to see if it would fix a bug that had been discovered, to no avail. Ran git bisect, and within about 10 minutes discovered the lines of code that caused it!
@jamesdoc It was sooo useful today! My code all looked like it should have worked. It should have. I tried some otherwise useful refactors to try and see if they’d help, but they didn’t.
Bisect found that I’d accidentally removed a line of code that works around a SwiftUI bug when I did some previous refactoring, by taking me to the exact commit I made the change in.