@DreamingPiggy@tapthaker Have you used this flag before? I couldn’t find any documentation about how to build a macro it understands, and the only user I found was apples own tests for the swift compiler
Follow Apple’s tutorial and convert your code from ObservableObject to Observation, and your build times may double.
https://t.co/MjmTq6SaGi
https://t.co/3ejNlYjYKh
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.
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.
@NeoNacho The IRS and California franchise tax board have extended the deadline till October 16th 2023 to give you time to use slurp juice on your apes, which i am told helps in some way
it really says something about games workshop pricing when a seven inch tall licensed space marine action figure is actually cheaper than many of their one inch tall space marine miniatures
so swift on iOS 15 apparently crashes if you use an existential with a primary associated type. Currently trying to understand why `let x: any Protocol<Y> ` is bad, but `x as? any Protocol<Y>` is seemingly fine