Jade Abraham
Jade Abraham
### Summary of Problem **Description:** Attempting to incorrectly use `forwarding` on a module-scoped variable or expression results in an internal error. This should just be an error message that `forwarding`...
Our docs are currently structured as follows - ... - Using Chapel - ... - Multilocale Chapel Execution - ... - Platform Specific - Major Platforms - ... - Networks...
Today, Chapel allows you to oversubscribe both tasks and locales. This allows users to emulate more cores or nodes. It would be nice to also allow over-subscription with GPUs. We...
The following code encounters an internal error during resolution ```chapel const arr = [1,2,3]; const cond = true; proc foo() const ref { if cond then return arr; else {...
The following code causes an internal error ```chapel coforall i in 1..10 with (ref sum2) { sum2 += i; } ``` It does not matter what the intent is, it...
I found that statements like `import A.B` and `use A.B` are not resolved correctly by CLS when a user tries to goto-defintion on `A` and `B`. `import A.B` always resolves...
We currently have limited-to-no support for using `complex` numbers in a GPU kernel. I tried a number of simple cases with complex numbers to get an idea of where our...
Removes mentions of alinux2 from the AWS docs, as alinux2023 is the preferred OS and pcluster 3.10+ supports it. While there, makes a few other tweaks to the docs (like...
I came to the unfortunate realization while working on the binarytrees benchmark that no matter what all Chapel classes have as their first element a "super" field. This means that...
I have found the following situations where the 'domain' keyword/typename is not allowed, where I think maybe it should be. All of the following situations result in syntax errors. This...