|
|
|
|
|
by papln
2475 days ago
|
|
> But I suppose that's difficult to visualize in a well human-readable way. It's not. The type-checker must have constructed a call stack of inferred types in order to find the violation, so it simply has to print all the calls (source line and line number) and the types it deduced, and let the programmer (or IDE) compare that to the code in context and look for surprises. |
|