-
Currently only a limited number of statements/expressions are shown in auto-completion, but I see this as a massive opportunity to support more common Chapel idioms.
# Common Idioms
## Spawn on …
-
### Summary
While trying/learning to write a tree-sitter parser for Chapel, I managed to accidentally construct a grammar that runs through the `generate` phase quickly, but hangs during `parse` (whi…
-
@tshimanga has been working on a locking contention issue, where the threading used in `libpq` conflicts with Chapel's native threading methods. Or at least it appears to.
-
As as Chapel Programmer, I want to be able to have a Chapel application compile as fast as a similar sized C program compiled with GCC so that modern programming expectations are met.
Acceptance Crit…
-
Should this program compile? If so, what overload of `foo` should
be selected?
```chapel
record rec { var x = 0; }
proc foo(const ref r: rec) const ref { return r.x; }
proc foo(ref r: rec) re…
-
Currently, we have the following environment variables for configuring Chapels memory allocation
- `CHPL_MEM`: the allocator to use for compiled chapel programs. Either `cstdlib` or `jemalloc`
- `…
-
The following code fails to compile on main with a potentially confusing error message
```chapel
proc foo(args) {
record R {
var x: args.type;
}
var r = new R();
writeln(r.x);
}
…
-
In #24155, we made expressions like `a < b < c` into syntax errors due to the ambiguity around whether the interpretation should be C-style (essentially `(a < b): int < c`) or Math/Python-style. Our …
-
-
# The Backyard Chapel
[https://scripturenews.com/BYC%20main%20page.html](https://scripturenews.com/BYC%20main%20page.html)