It takes a version result and not only updates references but then also mutates the code base on the basis of the newly obtained references.
A Nix writer is certainly no good in-tree use case.
Hence, this PR tries to conceptualize a potential extension point for downstream packages which could implement writer implementations similarly as, today, nvfetcher_source provides source implementations.
Context
https://github.com/lilydjwg/nvchecker/pull/253 prototypes a "writer" implementation.
It takes a version result and not only updates references but then also mutates the code base on the basis of the newly obtained references.
A Nix writer is certainly no good in-tree use case.
Hence, this PR tries to conceptualize a potential extension point for downstream packages which could implement writer implementations similarly as, today,
nvfetcher_source
provides source implementations.