Vladimir Panteleev

Currently I do not have anything set up that generates first-party checksums. Well, the build is done on GitHub Actions, so, GitHub is the first party. But we could make...

Thanks! BTW, the likely reason why the LDC-produced binaries are smaller is that, by default and unlike DMD, it links to the runtime and standard library dynamically.

Yes. Note that the CI builds static/LTO versions of everything. You can request to just link the static standard library / runtime with `-link-defaultlib-shared=false`.

Well, `--du` is really only there for compatibility with tools that consume `du` output, such as `xdu`/`xdiskusage`. For anything else, I would suggest using `--export` and e.g. a `jq` script.

As a starting point, here is a `jq` script which should produce roughly the same results as `--du`: ```jq .totalSize as $totalSize | .root.data.represented.samples as $totalSamples | def descend(prefix): (prefix...

> With an exported json file of size 2.1 GiB, the jq command consumes about 20 - 30 GiB RAM on my computer. That is a lot. I think a...

Here is a `jq --stream` script: ```jq def updateState(item): item as [$jsonPath, $value] | # Start with previous state as base # Clear output . * {"output" : []} |...

Two main reasons: 1. It's not clear where the mount point directory should be created, and how to guarantee that it is cleaned up. (Maybe the answer is a private...

Yes, this becomes a philosophical question. Should the tool cater to its average user, or to the user who is using it the most?  > But once the user...

OK, I'm convinced. Will accept a patch which adds `unshare`+`mount`, behind a switch at first, then default in a later version.