Closed martijnbastiaan closed 4 years ago
So, morally this seems like the right thing to do, but I want to make sure there are no unintended consequences. Can't think of any off the top of my head. CC @haskell/core-libraries-committee
yeah, this is pretty unoffensive to me.
@martijnbastiaan this needs a changelog entry before merging
@chessai Sorry for the delay, done!
Without this patch the following code:
gets parsed as
instead of
Note that
seq
already behaves like this.We had similar problems over at clash-lang/clash-compiler for our Clash-specific version of deepseq causing pretty bad memory leaks.