redo the entire lazy trees concept #7

New issue

Open

opened 2024-03-07 06:26:31 +00:00 by pennae · 1 comment

pennae commented

2024-03-07 06:26:31 +00:00

Owner

our plan for that is to fully strip back the input accessor infra they've put in place already, standardize on posix fs semantics because that's what nix was built on, decouple libexpr completely, and then start again from there
on a mountpoint-based system that synthesizes store paths for "lazy" sources, and is then taken apart by the external-to-libexpr fs shim
eg you'd get not /foo for a file foo in a zip archive but /nix/store/.mounted/source.zip/foo in the evaluator, and eval don't care

(ie, eat the accesses before hitting the actual fs [h/t jade])

lazy trees are busted. path semantics are unclear and often implemented incorrectly, accessors are semi-invisible and intrusive to the evaluator anyway. lazy trees should be reworked, probably on the basis of something proven: posix semantics and mountpoints our plan for that is to fully strip back the input accessor infra they've put in place already, standardize on posix fs semantics because that's what nix was built on, decouple libexpr completely, and then start again from there on a mountpoint-based system that synthesizes store paths for "lazy" sources, and is then taken apart by the external-to-libexpr fs shim eg you'd get not /foo for a file foo in a zip archive but /nix/store/.mounted/source.zip/foo in the evaluator, and eval don't care (ie, eat the accesses before hitting the actual fs [h/t jade])

❤️ 1

jade added the

performance

label

2024-03-11 20:02:00 +00:00

lix-project referenced this issue from a commit

2024-03-28 15:21:35 +00:00

progress-bar.cc: fix signed overflow

jade added the

Area/flakes

label

2025-01-19 22:37:25 +00:00

lix-project referenced this issue from a commit

2025-01-29 18:11:13 +00:00

Merge pull request 'lix: deal with util.hh removal' (#7) from jade/util-hh-removal into main

lix-bot commented

2025-04-05 19:58:22 +00:00

Member

This issue was mentioned on Gerrit on the following CLs:

commit message in cl/2947 ("libutil: trace unwinding through async tasks")

This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/2947](https://gerrit.lix.systems/c/lix/+/2947) ("libutil: trace unwinding through async tasks")

lix-project referenced this issue from a commit

2025-04-06 18:52:20 +00:00

libutil: trace unwinding through async tasks