Jade Abraham

I hit this debugging some codegen code. I have two fixes for this 1. A workaround is to compile with `--ignore-errors` 2. a fix is to switch the compiler to...

Noting that in https://github.com/chapel-lang/chapel/pull/26921 I have significantly improved our detection for slingshot and infiniband. After that PR is merged, a user running on a generic linux64 infiniband system should get...

I believe `csin` is missing because we use C++14 for GPU codegen, but rely on C99 complex number support. In C++14, `complex.h` may not implement all of the complex math...

Perhaps something analogous to `cmake.python-hints`? `cmake.cc-hints`? I feel like that meshes well with the cmake toolchain files, as setting CC/CXX unexpectedly might interact badly with them.

Great, glad to hear the bug has been fixed and that the fix will be available soon. Thank you

The latest release is out and seems to have fixed this for us. Thanks!

I also want to note that if/when we do this for our standard modules, we should introduce a linter/smoketest to enforce testable examples in docs. Essentially disallowing `.. code-block:: chapel`....

As a data point, grepping for `.. code-block:: chapel` in the standard library - `modules/standard`: 85 occurrences - `modules/packages`: 94 occurrences - `modules/dists`: 26 occurrences - `modules/internal`: 25 occurrences Not...

Yes thats a problem with the literal include approach. You can no longer build the docs from a tarball. We need to also include the sources, which implies to me...

To add to this, the reason all Python objects take an interpreter original was to prevent users from shooting themselves in the foot. If `new Value(...)` doesn't take an interpreter...