Please fix `.init` property

[Jonathan M Davis]

On Monday, January 8, 2024 11:16:42 PM MST FeepingCreature via Digitalmars-d 
wrote:
> On Monday, 8 January 2024 at 18:03:00 UTC, Jonathan M Davis wrote:
> > On Monday, January 8, 2024 3:57:52 AM MST FeepingCreature via
> >
> > Digitalmars-d wrote:
> >> Force default values to be typed immutable?
> >
> > That would require that there be a general way to copy an
> > immutable value to a mutable one, because the object must be
> > mutable after it's been default-initialized.
> >
> > Bastiaan's suggestion to make such cases illegal is probably
> > the only sane way to prevent these kind of issues, though I
> > think that it would have to be an error to have mutable
> > indirections with an allocation rather than illegal to point to
> > any allocations; otherwise, stuff like SysTime's member which
> > is Rebindable(immutable TimeZone) becomes illegal.
>
> Yes, the point of making it forced `immutable` is exactly to make
> the problematic cases illegal. Don't even think about deepcopy vs
> array vs object etc., just let the const system handle it.

Maybe? My gut reaction is that there's likely to be an issue with that, but
at a glance, it seems like it might work. So, it could be a really good
idea, but there may also be some subtlety that I'm not thinking of at the
moment.

- Jonathan M Davis