-
Currently this code:
```chpl
class Block {
proc init(targetLocales: [] locale) {...}
}
var targetLocales: [....] locale?;
populate targetLocales;
... new Block(targetLocales!) ...
```
d…
-
Depends on #898 and #1333
Use the index to provide go to definition for methods.
Might depend on exploring using a control flow graph (CFG) to implement reaching definitions. While we do not pro…
-
Split-off from #13518.
Currently, `begin`, `cobegin`, and `coforall` always create qthreads-style tasks. However, for recursive algorithms, we would like it be easy to create tasks only when there …
-
Related #14271 #14104 #8792
Feature request. Improvement. (This is more of a brainstorm than a concrete proposal.)
Provide a means to annotate locations of runtime-initializing a container of non-…
-
This issue asks how to put all the features together for a coherent update of our genericity story.
Here is my opening proposal:
* Require `(?)` when using a generic type, #21455
* Require `?` …
-
As of Chapel 1.32, we do not support a public way to get an `unmanaged` handle to a managed class that doesn't affect the lifetime of the object. Prior to Chapel 1.31, the way to do this was with a ca…
-
**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…
-
This is a speculative issue based on the way that type parameter constraints are implemented. This is a discussion of a possible future language change, not one that will be adopted in the near futur…
-
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.
…
mppf updated
10 months ago
-
# Background
By far the most common cause for panics (for me at least) is nil pointer dereferences - the billion dollar mistake.
This problem isn't unique to golang, but a number of languages ar…