@0zne That’s because the strategy conflicts with the fact that they still have PMs. If they gutted all of them then the replies would look a little different here.
@eneko Agreed with the cognitive load part. The access level handles the method call but I’d write a UI test against this to validate the save action and use of explicit unwrapping here.
For months I’ve heard ex-Twitter employees weren’t good enough, weren’t hardcore enough, were the leftovers of the bunch. What about now? If we were so easily disposable, why the cease and desist?
@ffrederick7@bmwblog I agree. DCT is far from dead as far as PDK performance goes from Porsche. Pretty bold statement of him to generalize that DCT is dead as if other manufacturers aren’t still utilizing them. Reasons why I’m keeping my DCT F87 forever.
Macros def are my favorite feature added since the language itself, I found the part in the “Expand on Swift macros” video explaining context.diagnose(DiagnosticMessage) key in making sure its used as intended.
@tiborbodecs Awesome job on the beginners guide. I think it would be nice to point out even for beginners that the macro’s usage should be governed for example here guarding against DeclGroupSyntax itself that it is a struct (or class if you intend for it to be also).
@tiborbodecs From the moment I watched the videos I knew this would single handedly be the most powerful thing we’ve had in the language since its inception.
@rubencodes The published part as we may see it is gone from the declaration level but the values themselves are being published from somewhere similar to how KVO works so it isn’t magic per se.