It took me a little bit to find it (link was hidden behind the gray Show More “button” on YouTube), so here’s the text proposal and discussion.
Reading through that proposal a bit, I don’t really follow what the advantage of this is over adding “replace example.com/foo => /path/to/foo” in the current go.mod? That works well for me anyway.
I think the idea is that you have multiple related modules and don’t want to accidentally publish a version with the replace statements included.
I can’t recall seeing a video like this for an alpha language feature before.
It’s not an alpha language feature, it’s a proposal (although it seems likely it will be accepted).
The demo was funny to watch because “Schmutz” translates to filth or dirt in german and “Schmutz Tool” is how I sometimes call tools that suck 😅
In more seriousness, I think this will be pretty helpful when trying to patch some external dependency.
It’s not an unintended meaning. In the US, the Yiddish word schmutz (which no doubt is from German originally) is part of popular culture.
Slowly circling back to bazel workspace