[Spark2014-discuss] Not null access constant in SPARK
roderick.chapman at googlemail.com
Mon Nov 2 08:45:59 CET 2015
Let's take a step back: what problem are you trying to solve
that requires the use of "not null access constant"? There might
be an alternative idiom that is allowed in SPARK...
Do you, for instance, want to use the "new" allocator, or just
create a table of values using the 'Access of other constant objects??
All the best,
On 01/11/2015 21:52, David Lesens wrote:
> I was wondering why “not null access constant” is not supported in SPARK
> Is it because there is a risk with this construct? (I don’t see any risk)
> Or is it just because the principle of SPARK is to not support access,
> even if it is safe
> In this case, is there any plan for the future of SPARK to support “not
> null access constant”?
> Project spark2014 discuss mailing list
> discuss at spark2014.forge.open-do.org
More information about the Spark2014-discuss