Naoufal Medouri
Axel Le PennecConfirmed by Apple 🫡
Rhys Morgan@alpennec is this cause they get converted to the dynamically replaceable functions thing they added basically for Previews, whereas constants/properties need full recompilation?
@rhysmorgan I'm not sure I understand your post. Can you clarify please?
@alpennec Ah, sorry! From my understanding, Swift/Xcode Previews are based on the idea of generating dynamically replaceable functions: https://fatbobman.com/en/posts/how-swiftui-preview-works/#:~:text=It%20specifies%20a%20method%20as,previews.%20See%20Swift%20Native%20method
Since a computed property is effective syntactic sugar for a () -> T function, I wonder if Previews treats them exactly that way, and can more easily “dynamically replace” the computed value, whereas using a property would require true recompilation of that view?
Since a computed property is effective syntactic sugar for a () -> T function, I wonder if Previews treats them exactly that way, and can more easily “dynamically replace” the computed value, whereas using a property would require true recompilation of that view?