opDispatch swallowing errors really sucks

[Sebastiaan Koppe]

On Friday, 10 January 2020 at 14:58:47 UTC, Adam D. Ruppe wrote:
> Did you typo it? Is it proxying a function call with wrong 
> arguments? Who knows. Here's my proposal: if opDispatch is 
> considered, its errors get printed. If you don't want that 
> spam, use a template constraint to remove it from consideration 
> entirely.

Yeah, that one is terrible. I bumped into it myself when I wanted 
to give the end-user a nice error message at compile time, 
instead what he got was a cryptic no property error.