Date: 2018-04-20 17:09 Sender: David MacQueenIn 110.82 this bug is gone, and the "binding not exhaustive" warning is given.
However, when executed, this example should raise the Bind exception when [1] does not match the pattern nil. It looks like the let binding has been improperly optimized away so that it is not executed. So this reveals a different bug in the optimizer, which is changing the dynamic semantics of the code. |