See comments below. /Erling
On 2016-10-01 23:25, 'Pascal Jasmin' via Programming wrote:
immutability is a "user experience". In a sense, (other than memory mapped files), there
is already a (very common) "return new value" semantic to operations which may be
understood as immutability.
Yes.
A logically immutable array/language though would mean reassignment would be
illegal. As I understand things anyway.
Yes, and in explicit J we work with reassignments and in tacit J we
don't? In tacit J we have non-mutable data?
What I'm discussing is the implementation. If it is a good idea to have
non-mutable arrays internally or not. To build J on top of a non-mutable
array class or to build it on simple arrays, which I, without knowing,
assume it is mainly built on today.
The related user interface experience is performance.
Maybe the possibilities to parallelize J is related, and the user
interface design related to this possible parallelization.
----- Original Message -----
From: Erling Hellenäs <[email protected]>
To: [email protected]
Sent: Saturday, October 1, 2016 3:56 PM
Subject: Re: [Jprogramming] Non-mutable arrays
On 2016-10-01 15:40, 'Pascal Jasmin' via Programming wrote:
Forcing immutable only arrays is not an option for this language if it is to
remain compatible with itself
Someone wants to give a more specific explanation to this? What in the
language prevents immutable only arrays?
/Erling
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
