chapel
chapel copied to clipboard
chapel-lang
a Productive Parallel Programming Language
### Summary of Problem **Description:** I accidentally wrote `iter init` instead of `proc init`, as I should. Rather than producing a compiler error about why using an initializer as an...
### Summary of Problem Hello, while updating some 1.33.0 code to 2.0.0, I faced something curious. Here is the reproducer: ```chapel use CTypes; record R { var arr: c_array(c_int, 10);...
PR #21872 updates the testing in `test/llvm/abi/aarch64/export-vs-c.chpl` to match the current behavior for that test. However, it is our goal to match the LLVM IR emitted by clang exactly for...
### Summary of Problem **Description:** This issue documents a workaround in the compiler, of a known issue with `const` pointers in generated C code with ICC. After https://github.com/chapel-lang/chapel/pull/24809 caused `c_ptrConst`...
Some code in our standard library works by default-initializing a value of a certain type, and then checking this value to see if various methods on it resolve. For instance,...
### Summary of Problem **Description:** The user can define a hash function that throws, but only so long as the hash function is not defined inside a module. Once the...
### Summary of Problem **Description:** We've deprecated inferring a method to be `ref` if it modifies its `this` argument. If a hash function happens to be `ref`, though, you will...
[Feature Request]: Export functions with arrays of strings as arguments for Python interoperability
### Summary of Feature **Description:** Today, in exported functions for Python you can: - accept string arguments - return strings - accept array arguments with numeric element types - return...
### Summary of Problem **Description:** Prior to the move from `c_string` to `c_ptrConst(c_char)`, we were able to export functions that took arguments of type `[ ] c_string`. Unfortunately, we did...
Here are some cases that can use better error messages: ### 1. `proc type` nature of `operator`s could be incorporated into error messages ```chpl record myRec { var x: int;...
