Well grown libraries are using the `@implicitNotFound` annotation to generate better library-controlled compiler errors, with advice given for what to do. It has its limitations of course, but proved very useful in many situations.
A search tree is cool, but it's not going to explain how to get a value when it has restrictions (dependencies).
`@implicitNotFound` still only gives you a top-level failure message. Also, my comment was aimed more at developers of libraries with complex implicit derivations not the consumers of such libraries.
A search tree is cool, but it's not going to explain how to get a value when it has restrictions (dependencies).