Shared Program:
anything attempting to use TupleSections or LambdaCase
current extensions.yaml
codeworld:
- []
haskell:
- LambdaCase
- NoTemplateHaskell
- TupleSections
Description
The given extensions are not implicitly enabled. The extensions.yaml above causes a parse error in the CodeWorld compiler, due to [] not being a valid String representation. This goes unnoticed, since there is a default value of no extensions in case of an error.
This file has been used on the build server even before it was added to this repository, so I cannot imagine this feature has ever worked correctly in the past. I swapped the live CodeWorld instance back to a version from June 2025 to verify and it did not work there either.
Fixing the syntax error does also not solve the problem. I changed the file to
codeworld: []
haskell:
- LambdaCase
- NoTemplateHaskell
- TupleSections
on the build server and deployed a new version, but extensions still do not work, even though this new config file is parsed correctly. So it seems there is another error preventing extensions from being loaded correctly somewhere in the compiler code.
Shared Program:
anything attempting to use TupleSections or LambdaCase
current
extensions.yamlDescription
The given extensions are not implicitly enabled. The
extensions.yamlabove causes a parse error in the CodeWorld compiler, due to[]not being a valid String representation. This goes unnoticed, since there is a default value of no extensions in case of an error.This file has been used on the build server even before it was added to this repository, so I cannot imagine this feature has ever worked correctly in the past. I swapped the live CodeWorld instance back to a version from June 2025 to verify and it did not work there either.
Fixing the syntax error does also not solve the problem. I changed the file to
on the build server and deployed a new version, but extensions still do not work, even though this new config file is parsed correctly. So it seems there is another error preventing extensions from being loaded correctly somewhere in the compiler code.