[m-users.] A question about in-place updating...

[Volker Wysk]

Am Dienstag, dem 29.08.2023 um 12:58 +1000 schrieb Julien Fischer:
> On Mon, 28 Aug 2023, Volker Wysk wrote:
> 
> > Am Montag, dem 28.08.2023 um 13:02 +0100 schrieb Sean Charles
> > (emacstheviking):
> > > 
> > > It's an interesting question for me to ponder at the moment! Given all
> > > that Mercury does, I am guessing that there are no ways to 'pin' a block
> > > of memory such that it can then be reused over and over, I have played
> > > around with bitmap but that's not really built for generic structures etc.
> > > I guess if it came to the crunch I could always re-code those things that
> > > need maximal performance in C but that kind of negates the reason I
> > > decided to write this game in Mercury.
> > 
> > What you describe seems to be a case for unique modes. See section 6 in the
> > Language Reference Manual.
> 
> In princple, yes. In practice, the limitations listed in section 6.3
> mean they're not really useful for that purpose.

In section 6.3: "The only destructive update in the current implementation
occurs in library modules, e.g. for I/O and arrays. We do however plan to
implement structure reuse and compile-time garbage collection in the
future."

Briefly, how are chances that this will happen in foreseeable future?

Cheers,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.mercurylang.org/archives/users/attachments/20230829/0b14d87a/attachment.sig>