Damian wrote:FWIW, I personally think this is _absolutely_ the right approach.
> Hence, I would argue, one ought to simply mark it with a trait:
Using a trait is a very visible, very obvious way to say what's going
on that is probably easier to remember than adding another keyword to
the [my|our|temp|let] group. While I, too, immediately understood what
'has' meant, I can't help but feel many people won't get it.
As others have pointed out, the problem with 'static' is not only that
> is retainedThese three, I think, show the most promise. Or the linguistically
> is preserved
> is kept
dubious "is once", maybe. The others like "is saved/stored/restored"
might be taken for serialization-style persistence.
David Landgren wrote:I think so... I thought about that too, but I think "persistent" is
> I expected to see 'is persistent' as a possible name. Or does that
> denote serialisation too much?
becoming synonymous with "serialized & stored" these days.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.