Under Review
over 1 year ago

feature request: allow to spedify type checking level in the monkey.jungle file

I dislike that typechecking has to be enabled/disabled globally 

- For my existing projects I really don't want to (/I won't) go back and fix thousands of type check warnings

- If I start a new project I might use type checking

I propose to add a new keyword to the monkey.jungle file which adds a new keyword:

typechecking = [none | gradual | informative | strict]

Having this would enable you to choose on a per project basis if you want type checking on or not for that project.

  • "However i realize this needs a little bit of thinking, because you'll need to "merge" the arguments given in the VSC settings and in the jungle file"

    Well, an override of options is already happening in VS Code with User, Workspace and Folder settings, so it's nothing new. Any concern about command line options being overridden vs merged can be sidestepped (in this case) by using the specific Type Check Level option instead of setting it via command line options.

  • If you use VS Code you can set the type-checking level in the workspace settings.

    If you have a multi-root workspace (with multiple projects), you can set the Jungle files, Manifest file, and Type Check level (but not anything else) on a per-folder basis. (The lack of other options seems like a weird limitation.)

  • I thought about the same problem, however i would even suggest to have a way to set the arguments to the compiler from the monkey.jungle file (for example a certain project has to be compiled with -O2).

    However i realize this needs a little bit of thinking, because you'll need to "merge" the arguments given in the VSC settings and in the jungle file, and i think (but need to discuss it probably) the settings in the jungle file need to override the settings in VSC (per parameter, so if I have in VSC: -l3 -O0 and in monkey.jungle: -O2, then the actual arguments should be: -l3 -O2)