refC is temporary scaffolding holding up part of the current Idris 2 / Idriç structure. It cannot necessarily be removed today without making the whole structure fall down and creating pointless cleanup work.
But it is frozen scaffolding now. Put caution tape around it:
- Do not build new code on refC.
- Do not add new refC assumptions, APIs, ABI commitments, fixtures, or acceptance criteria.
- When touching existing refC-dependent code, keep the dependency contained and visible.
- Design all new work as though refC is already absent.
- Remove existing reliance brick by brick as direct backends and other secure supports become real.
This issue is not an order to delete refC immediately, and it sets no removal date. It is an order to stop increasing the load on it.
Same caution tape in the other repositories
Repositories in the same Idriç-bearing evidence set with GitHub Issues disabled: isomorphisms/hopf_fibration, isomorphisms/fieldmouse.
refC is temporary scaffolding holding up part of the current Idris 2 / Idriç structure. It cannot necessarily be removed today without making the whole structure fall down and creating pointless cleanup work.
But it is frozen scaffolding now. Put caution tape around it:
This issue is not an order to delete refC immediately, and it sets no removal date. It is an order to stop increasing the load on it.
Same caution tape in the other repositories
Repositories in the same Idriç-bearing evidence set with GitHub Issues disabled:
isomorphisms/hopf_fibration,isomorphisms/fieldmouse.