Russ Cox

Note that the new `clear` builtin will shorten the implementation of these, making it even easier to maintain them outside the standard library.

Based on the discussion above, this proposal seems like a **[likely decline](https://go.dev/s/proposal-status#likely-decline)**. — rsc for the proposal review group

No change in consensus, so **[declined](https://go.dev/s/proposal-status#declined)**. — rsc for the proposal review group

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

-C=off is ambiguous but it doesn't seem likely to arise in practice, and it's consistent with most of our other settings that can be disabled (and you can use -C=./off...

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group

No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

The general approach sounds right but I'm not sure we can make the behavior completely portable. What do we do about paths with backslashes or colons? Are those insecure on...

Also what about symlinks? Do we reject symlinks containing absolute or other "insecure" paths? A tar file could contain x -> / followed by x/etc/passwd