Currently, the architecture of the CLI is based on (sub)commands and options. Commands are expected to be provided as the first argument, and do effectively decide which feature is to be used. OTOH, options provide parameters to the commands. However, there is no syntactical difference, as both commands and options start with -- or -i. As a result, we rely on properly formating --help and on

In order to support package managers better, which write their retrieved data typically in unique paths, it would be nice to be able to declare multiple base_dir paths to translate absolute paths in relative ones.

For example a package manager would have the following paths in its cache:

~/data/libA/1.0.0/acme/stable/package/63da998e3642b50bee33f4449826b2d623661505/include/libA/myheader

This is the same issue as #28 , though written in English.

Background and foreground colors of brace characters change when approached by the caret, if the option "highlight matching braces/parenthesis" is ticked. When the caret leaves these characters, however, background returns to its original color, while foreground doesn't.

Illustrated with screenshots in #28 .

Bitwise operators are supported for now, also support addition and subtraction for INTEGERS ONLY.

Currently, decompilation of Windows executables produces unreadable and/or semantically wrong output because the signatures for most of the Windows API functions are missing. We should add signatures for at least the most commonly used ones.

Currently compiling Data.Either.Nested takes about 10 seconds. It emits about 84k lines of code! So we should (a) investigate optimization passes to remove the lines to output and (b) make it run fast even when generating large files like that.