There are conceptual problems that we encounter when Avail has to have knowledge of when working with module roots that it can't learn by scanning the module roots or through any other "first class" subsystem system presently available. The AvailProject is used to configure Avail externally. By integrating AvailProject more deeply as a proper subsystem of Avail, we give Avail the power to know internally about the external and internal shape of any Avail codebase without having to infer information from scans. To that end we will:
- Integrate the
AvailProject directly into the AvailVM
- Extend
AvailProject to explicitly configure headerless modules
- Remove the
Corpus section from Avail header files
- Explore other potential uses for
AvailProject to enable new features for Avail
@markATavail @leslieATavail @toddATavail
There are conceptual problems that we encounter when Avail has to have knowledge of when working with module roots that it can't learn by scanning the module roots or through any other "first class" subsystem system presently available. The
AvailProjectis used to configure Avail externally. By integratingAvailProjectmore deeply as a proper subsystem of Avail, we give Avail the power to know internally about the external and internal shape of any Avail codebase without having to infer information from scans. To that end we will:AvailProjectdirectly into the AvailVMAvailProjectto explicitly configure headerless modulesCorpussection from Avail header filesAvailProjectto enable new features for Avail@markATavail @leslieATavail @toddATavail