Closures are unique because they may capture additional context and store it in a separate context object. So checking if the function pointer is the same is not sufficient to determine if closures are equal. You must also check the captured context—something that Swift does not do.

To clarify, I’m referring to properties stored on the view, not the contents of `body` or other functions/computed properties on the view.

Are you referring to `body`?
That’s a function, not a closure.

Swift views that only have trivial data types as properties are themselves considered “plain old data” (POD): xcancel.com/SwiftUILab/s...

You can check yourself by creating different views and calling _isPOD() on them.

You may have misread:
> After modest administrative expenses half the funds donated to FTDWS go equally to Partners in Health and Save the Children. The other half go to 30+ charities recommended by the participants of the Project for Awesome.

Though you’re right that it would be more efficient.

I think it should run with as little as 8GB

> WCAG is the gold standard... *Some governments make them a legal requirement.*

The legal requirement thing is our biggest issue. Unfortunately we run the risk of someone suing if we don’t meet WCAG2. Design knows it’s flawed, but Legal doesn’t want the risk.