Closed alanz closed 7 years ago
Another glitch, I think this was because at the time we couldn't decide which keyword to pick -- for this use case a case can be made for both :)
Still, over time we always just use "lazy" so let's drop the other one!
Thanks a ton @alanz!
On Tue, Mar 21, 2017 at 8:02 AM Alan Zimmerman notifications@github.com wrote:
Both Lazy and Strict are parsed identically
<|> (reservedToken "Strict" >> liftM Lazy lazyVarP ) <|> (reservedToken "Lazy" >> liftM Lazy lazyVarP )
This seems to indicate that saying Strict foo is actually making it lazy?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ucsd-progsys/liquidhaskell/issues/973, or mute the thread https://github.com/notifications/unsubscribe-auth/ABkuOHsx-W327I6xMBnZ1vWFcM3O8NtCks5rn-aFgaJpZM4Mj8CX .
Both
Lazy
andStrict
are parsed identicallyThis seems to indicate that saying
Strict foo
is actually making it lazy?