Robert Hensing<p><span class="h-card" translate="no"><a href="https://c3d2.social/@katzenmann" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>katzenmann</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@nixos_org" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nixos_org</span></a></span> One of the hurdles is stabilizing an underlying feature like <code>fetchTree</code>. <span class="h-card" translate="no"><a href="https://fosstodon.org/@domenkozar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>domenkozar</span></a></span> is doing some great work on that with an alternate implementation of it in <a href="https://functional.cafe/tags/SNix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SNix</span></a>, exposing some of the unfortunate choices that all <a href="https://functional.cafe/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Nix</span></a> implementations should backtrack on.</p><p>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.</p><p>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.</p>