Restrict blanket impls

[muja]

Blanket impls like these are very irritating because they get suggested by the IDE in completely unrelated places e.g. I was looking for a contains method on some container, and my IDE suggested this impls method. And if you accidentally select it, it will import it and if it happens to compile, your code will do some very weird things. I had this many years ago with chumsky 0.8 where I accidentally imported a trait that had a .len() blanket impl which always returned 1, and it was extremely hard to debug.

Maybe it's possible to restrict these impls somewhat, or, if not at all possible, make the method name a bit more specific to this library to avoid any possible confusion

[zesterer]

I'm happy to accept a PR for a name change since this is intended as a semi-internal trait. That said, I think the underlying problem here is with your IDE. Assuming the IDE uses an LSP server like rust-analyzer, do you know of a way to deprioritise/hide those implementations?