-
### Summary of Problem
Variables that have not been default initialized but are accessed in a `coforall` loop cause an internal error. This should result in a compiler error saying that the variable …
-
Currently the ``binarySerializer`` and ``binaryDeserializer`` types add some additional binary data for certain types to make it easier to read types, or to deal with errors. For example, classes begi…
-
Is there any reason why `Typed::Failure` and `Typed::Success` use `T.nilable(Error)` and `T.nilable(Payload)` internally?
Since those types are `type_member`, the user should be in control on making …
-
**Note, 2023-01-17**. This proposal is on hold indefinitely due to serious API concerns. The GOEXPERIMENT=arena code may be changed incompatibly or removed at any time, and we do not recommend its use…
-
Currently `set.remove()` does not return the removed element at all, instead choosing to drop it on the floor. This choice was inspired by Python, where `set.remove` also returns `None` instead of the…
-
Related to #18665 and #16508.
Also related to a common error in declaring recursive class types (in details)
I think there have been issues about that but I haven't found a link to one yet.
…
mppf updated
6 months ago
-
As a Chapel programmer, when I write:
```chapel
class C {
var x: int;
}
var myval: shared C? = new shared C(23);
proc myfunc(): shared C {
return myval!;
}
myfunc();
```
I would…
-
### Problem
In strict mode, instance variables need to be declared early. This is quite verbose in a common case of a caching variable in a method. For example:
```
sig {returns(Foo)}
def foo
…
-
I discovered this while implementing DistributedMap. maps today have a `clear` method and I was toying with making distributedMap a class so that there could potentially be an inheritance relationshi…
-
We are preparing for the Chapel 2.0 release where the language is stable. This issue asks about whether or not we are confident that we want to keep the ref-maybe-const feature as it stands for 2.0.
…