A potential solution to having to keep restating ~Copyable and ~Escapable constraints

I've been writing a lot of code lately using ~Copyable and ~Escapable, and I keep butting heads with the compiler automatically inserting Copyable and Escapable constraints on protocols that refine ~Copyable and ~Escapable in generic contexts. This is probably the biggest ergonomics complaint people have about these protocols as it stands, and I have been trying to figure out how we could address that. The other day I had an idea, though I'm not sure we can retcon it at this point: Fundamentall...