Static property wrappers and strict concurrency in 5.10

[dmt (Dima Galimzianov)]

@jrose

not only is there no setter, but the value you get will be the same each time (i.e. it’s guaranteed to be locally cacheable, and eliding gets is a valid optimization). Of course, this applies to some computed properties too, and we don’t have a way to expose that.

That reminded me about a related discussion [Pitch] Allow Accessor Macros on Let Declarations
Don't know if there was any progress though.