Michael Ferguson
Michael Ferguson
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...
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...
Currently, Chapel has pretty good C interoperability (through `extern` blocks, `c2chapel`, `extern` and `export` procs/vars). It comes up semi-regularly that one needs to work with a C++ library. However, there...
This issue is a spin-off from issue #24788. That issue identified several problems with the `regex` initializer that have to do with `posix` mode regular expressions. One wrinkle that continues...
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...
Fixes the summary line for HashedDist for issue #25667. Trivial and not reviewed.
### Summary of Problem **Description:** I have to declare the return type for a function because it is recursive, but when I do that, it increases the memory usage significantly...
It's common to see Chapel code like this: ``` chapel writeln(a, " ", b, " ", c); ``` because otherwise, writeln will glom together the output: ``` chapel writeln(1, 2,...
### Summary of Problem **Description:** I'd like to `min reduce` arrays of integers (so that the result is an array of minimums in each position). I am led to think...
### Summary of Problem **Description:** I've run into an internal compiler error when calling walkDirs. It turns out that I wanted to call findFiles rather than walkDirs anyway. But I...