I fiddled with alternative representations for a while and didn’t make
any progress—it was too easy to end up with code explosion in the
presence of any unknown calls—but I seem to have found a RULES-based
approach that works very well on the examples I’ve tried. It’s quite
simple, which makes it
Hi Andreas,
"Op" stands for "Operation" but it's not very obvious (ironically when I
started this renaming work one of the motivation was to avoid ambiguous
acronyms... failed).
The idea was to separate Core types from Core
transformations/analyses/passes. I couldn't find something better th
Hello devs,
While I looked at the renaming a bit when proposed I only just realized
we seem to be using Op as a short name for optimize.
I find this very unintuitive. Can we spare another letter to make this
GHC.Core.Opt instead?
We use opt pretty much everywhere else in GHC already.
Cheers
An
