I’ve asked in the last thread and didn’t get an answer so I will repeat my question here
I thought we decided that lazy trees in their current form have a negative impact on the language due to introducing non-determinism?
Do your customers not care about deterministic path semantics? Are there any surveys showing that people are okay with this? Are people made aware that lazy trees change language semantics?
There is a concern about that on that pull request, however we have not seen any real world impact when path ordering and path equality are different between executions. Given the instability of source path hashes in general, I don’t believe this to be a compelling or concerning semantics change to any use case. I’d be happy to be shown wrong, though!
Congrats! If you could make it clear for those items listed in the post, whether they are features that are new in Nix or DetNix. It’s probably the latter but I think it takes a thought or two to come to that conclusion and I only have so many per day.
Anyone with a large monorepo is locked out of flakes anyways for performance reasons, so observing an absolute path already exposes them to non-determinism.