Thank you for the answer.
A few more questions...
- I assume that for
~Copyablethat's the only way to implement getters and setters right now? - For types that are
Copyable, if for some reason one wants to implement logic that operates "in memory" instead of copying, can these be used too? - Is it possible to have both
getandsetandunsafeAddressandunsafeMutableAddressfor same property (ofCopyabletype? ). How does it work?
PS: Are these not documented at all? (Comments within the compiler code would be better than nothing). Are they supposed not to be used in code external to the language implementation?