@katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree
. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.
This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.
For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.