bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>, Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Darshit Shah <darnir@gnu.org>
Subject: Re: immutable string type
Date: Sun, 29 Dec 2019 20:03:49 +0100	[thread overview]
Message-ID: <287084bb-467d-fe4a-2999-dbb287a0c778@gmx.de> (raw)
In-Reply-To: <b85826d8-8986-25fd-bea1-c717e8bf3820@cs.ucla.edu>


[-- Attachment #1.1: Type: text/plain, Size: 525 bytes --]

On 29.12.19 19:49, Paul Eggert wrote:
> On 12/29/19 4:07 AM, Tim Rühsen wrote:
>> Introducing a stronger 'const' could be helpful in some situations
> 
> D has 'immutable' for that. It doesn't work as well as one might think.

It all depends on the implementation / definition of 'immutable' and how
it is used. Not sure what the actual problems are within D, though.

A quick web search didn't give me any complaints about immutable in D.
Do you have some examples or can you elaborate a bit ?

Regards, Tim


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-12-29 19:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28 11:17 immutable string type Bruno Haible
2019-12-28 13:35 ` Tim Rühsen
2019-12-29  9:45   ` Bruno Haible
2019-12-29 12:07     ` Tim Rühsen
2019-12-29 18:49       ` Paul Eggert
2019-12-29 19:03         ` Tim Rühsen [this message]
2019-12-30  3:11           ` Paul Eggert
2021-01-18  8:17       ` Bruno Haible
2019-12-28 16:54 ` Ben Pfaff
2019-12-29  9:29   ` Bruno Haible
2019-12-28 18:15 ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=287084bb-467d-fe4a-2999-dbb287a0c778@gmx.de \
    --to=tim.ruehsen@gmx.de \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=darnir@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).