chapel
chapel copied to clipboard
chapel-lang
a Productive Parallel Programming Language
Today in the LinearAlgebra module we write matrix-matrix multiplication with e.g. `A.dot(B)` or `dot(A,B)`. However, it would be more math-like if we had an infix operator for this. It's my...
### Summary of Feature **Description:** `$CHPL_HOME/util/printchplenv` has an anonymize flag that allows printing Chapel settings without details like the path to the user's installation of Chapel. The Chapel compiler itself...
This is not a show stopper at this point. Current work around is to not include the header file on the compilation command. Of course then I get a linking...
Consider this program: ``` chapel module Main { writeln("initializing Main"); module Submodule { writeln("initializing Main.Submodule"); proc foo() { } } proc main() { import this.Submodule; Submodule.foo(); } } ``` At...
This weekend, while thinking about the performance difference between [nbody3](https://github.com/chapel-lang/chapel/blob/main/test/studies/shootout/submitted/nbody3.chpl) and the current [nbody-blc](https://github.com/chapel-lang/chapel/blob/main/test/studies/shootout/nbody/bradc/nbody-blc.chpl), which uses `foreach` loops rather than `param`-unrolled loops, and how to minimize the differences between the...
In attempting to add a dependency to a mason project (e.g., `mason add [email protected]`), I got the following error: ``` error in listDir(): /Users/.../.mason/mason-registry/Bricks/: No such file or directory No...
### Summary of Problem `in` intents on functions can cause out of memory issues that crash chapel programs. **Description:** This issue is prompted by a bug reported by one of...
Today, writing `for _ in 1..10` will lead to a generic "syntax error". This is not an ideal error message, but seems like it ought to be easy enough to...
Today, you can write the following: ```Chapel var x = (_, ); ``` Which parses fine but gives the following, relatively confusing error message: ``` loop.chpl:1: In module 'loop': loop.chpl:1:...
Currently, the compiler applies `MOD_STANDARD` to code parsed from `modules/packages`. This means that this code isn't being checked with unstable warnings and a variety of other checks. At the same...