Unclear why two steps are required for a single opt-in.
It has happened on multiple projects that I uncomment the flag but forget to also toggle it.
An alternative is leaving as a comment with = true but the approach here has the advantage that changes upstream to the attribute paths will trigger eval errors/warnings when they happen, not when the flag is next uncommented, minimizing distance between cause and effect.
Unclear why two steps are required for a single opt-in.
It has happened on multiple projects that I uncomment the flag but forget to also toggle it.
An alternative is leaving as a comment with
= truebut the approach here has the advantage that changes upstream to the attribute paths will trigger eval errors/warnings when they happen, not when the flag is next uncommented, minimizing distance between cause and effect.I have:
developbranchhlint .(lint found code you did not write can be left alone)$(nix-build -A selftest --no-out-link)nix-build release.nix -A build.x86_64-linux --no-out-link(orx86_64-darwinon macOS)