APACHE-2.0 License
CAUTION: These features use a work-in-progress resolver for Chapel called Dyno to further inspect your code. To enable these features, use Dyno by setting
chapel.chpl-language-server.resolver
totrue
. Enabling the Dyno resolver for most Chapel projects will likely result in a crash.
After installing the extension, follow these steps to make sure VSCode is set up to use the extension.
The extension can auto-detect your CHPL_HOME
, just open a Chapel file. The extension will prompt you to select an existing Chapel install to configure your editor. If you don't see your value of CHPL_HOME
or don't know the right one, run chpl --print-chpl-home
to get the right value. If the automatic installation fails, you can explicitly set your CHPL_HOME
in your VSCode settings.json as "chapel.CHPL_HOME": "/path/to/your/chapel/home"
.
The extension can also auto-build the Chapel language tools and will prompt you to do so if they are missing. If you prefer to build them manually, run the following: (export CHPL_HOME=/path/to/your/chapel/home && cd $CHPL_HOME && make chpl-language-server && make chplcheck)
tar xzf chapel-VERSION.tar.gz
CHPL_HOME
("/path/to/unpacked/source/chapel-VERSION"
) and follow the steps for an existing Chapel build.Individual linter rules in the Chapel linter, chplcheck
, can be turned on or off. This is done by adding arguments to your VSCode settings. For example, the following turns on the NestedCoforalls and UnusedFormal rules.
"chapel.chplcheck.args": [
"--enable-rule", "NestedCoforalls", "--enable-rule", "UnusedFormal"
],