Russ Cox

We can already cross-compile with our own toolchain. No need to add the complexity of another toolchain. The CC= issue is easy to fix, as is #53862.

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

@laboger That sounds like an interesting idea. Thanks. I filed #54375.

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

I certainly see the utility here but adding `**` has various knock-on effects that may not be obvious. For example, `*` matches symlinks to other directories. `**` cannot, at least...

This issue does remain open. What's confusing is that GitHub has linked just above your comment to issue Shopify/themekit#102, which is closed.

Like Ian said, I'm not convinced we should enumerate the many possible glob extension syntaxes that exist but are not implemented by this function.

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

This is undocumented, so it is probably OK to remove. If we replace it with internal-only things then no one will be able to see it. I don't think we...

Will record this as "discussion ongoing", but it also sounds like a prototype is needed before making a decision. If that will take a while we can also move this...