Proposal: Consider structs with explicit local type parameters as local for impl

[scottmcm]

@mcy

This desugar is meant to indicate that path must be resolvable as a single trait

Sounds like

Idea: Paths in method names

Once again, we have a case in std of adding methods and people getting broken. I really don’t want to get stuck in the sad world where we can no longer add things without new a new extension trait every time, so I want to keep this allowed breakage, but maybe there’s a way we can make it a bit less annoying. Right now, the answer to getting the wrong method is UFCS. That certainly works, but there’s a massive gulf here—to control name resolution you need to give up on method syntax entirely, …