Restructuring for common and base
jonmeow opened this issue · comments
We have:
- //common
- //testing
- //testing/util
- //explorer/common
- //toolchain/common
We've been discussing the naming scheme in use (some context in docs, mentioned on discord), and I think where we agreed is:
- //common
- //testing
- //testing/base
- //explorer/base
- //toolchain/base
The principle here is that "common" indicates things which are really cross-component (explorer and toolchain), whereas "base" is the more shared stuff within a given component.
I'm be doing moves to effect this structure.
What do you (or others) think about keeping testing unnested, and basically unnesting any meaningfully named common component? Mostly wondering if that would let us have somewhat fewer directory components.
Per discussion on Discord -- I'd thought you'd preferred //testing move, but it sounds like not, so I'll just do //testing/util -> //testing/base.