<@U0BHS1Y07>: Well my solution is different (and f...

# language-proposals

[rocketraman]

@voddan: Well my solution is different (and for now, sufficient), so this is a theoretical discussion for now. This was all prompted by @natpryce comment about whether there needs to be an easier way to call the copy constructor given a KProperty. You asked for a use case. I provided one. Your approach to my use case didn't eliminate the need for what @natpryce was originally talking about, AFAICT.