RFC: Repository & Cabal Layout (Monorepo vs Multi-package)

[Ciznia]

Since this project have a lot of smaller part, possibly independent, i think we need to discuss of the folder structure early,
I have checked with cabal you can define a cabal.project and multiple *.cabal file to manage the overall build with cabal build at top level (https://discourse.haskell.org/t/monorepo-cabal-internal-libraries-vs-multi-package-cabal/7424).
However, this needs more attention since the opinions in that thread seem to be split, specifically because of the project context.

And it seems (need to be checked) that having multiple cabal file rather than a big cabal file will help cabal to cache build like not rebuild the parser if it or it's dependencies didn't change.

But i want your regards about how we structure things, since if we go the way of the .project file the only requirement seem to be that the multiple cabal packages doesn't have the same source dir, and that each packages in the project file be a folder, but can be anywhere

[Sigmanificient]

For codecov to properly works, (as we need to run each entry for coverage), we will need to combine them. We will need to dynamically parse the glados.cabal (or all the cabal files)

[renman-ymd]

Current Proposal: Decoupled modules to avoid a monolithic src/.

.
├── flake.nix
├── ast/
│   ├── ast.cabal
│   └── src/
├── compiler/
│   └── ...
└── vm/
    └── ...

Edit: Done in

• modularize repo into cabal packages #21