The problem is that the new cycle detection code doesn't know that we're looking for a type. If it knew, it could avoid reporting the cycle in favor of the subsequent error. Fixing this will likely require that we pass around a "context" parameter during type-checking which states the expectation for the expression to be checked (similar to the "top" parameter in the compiler's type checker). Not hard to do but possibly pervasive.
The text was updated successfully, but these errors were encountered: