Fabio Massaioli

The problem should be partially resolved by listening on `process.stdin` in place of `{ fd: 0 }`. I still don't know how to check whether the stdin handle is a...

Note that ESM modules may degrade performance because of the live bindings issue. See https://github.com/nodejs/node/issues/44186

First of all thank you for your work on this and sorry for the very late feedback. It is true, as you wrote in the proposal, that people can manage...

I opened a PR with a draft implementation for this proposal at #850 Technical details are discussed over there.

After thinking further about it, I believe the impact of leaking `garble map` output would be somewhat smaller than I thought initially. The path encoding by `x/tools/go/types/objectpath` uses names for...

Thank you @mvdan for taking the time to answer this. I have just rebased and tested the PR against the current tip. > In fact I expect the "map" subcommand...

> Perhaps hold off on spending too much time on the PR, because I'm not yet convinced about how to design this feature. Sure, the PR was always meant as...

> The main difference is that "map"-like functionality requires knowing in addition which objects (packages/types/methods) are actually obfuscated at build time, and which ones aren't. In light of the work...

> To be clear, you absolutely cannot match the obfuscation of garble build with the mechanism that you describe [...] we should not provide an alternative command that misleads users...

Thank you so much @mvdan for you efforts. I tested #904 via cloning and installing (via `go install .`) your fork [mvdan/garble-fork](https://github.com/mvdan/garble-fork), branch [reflect-pkgpath](https://github.com/mvdan/garble-fork/tree/reflect-pkgpath). The tip of the branch is...