[MLton] Selectors in -show-def-use output
vesa.karvonen at cs.helsinki.fi
Fri Feb 9 08:04:21 PST 2007
Quoting Matthew Fluet <fluet at tti-c.org>:
> So, it is probably not the right choice to expose the dummy variable in
> the def-use information. Somewhere in elaborate-core.fun is probably
> the right place to fix this.
Browsing the code, I realized that bindings whose definition has a bogus
region are not reported. So, I changed the selector function to use a
bogus region for the generated variable:
The enclosing pattern, however, is still given a non-bogus region and I
checked that the compiler seems to report unresolved record patterns
correctly. BTW, browsing the code (namely uses of Symbol.fromString),
I noticed that there may be other places where it might be appropriate
to use a bogus region.
More information about the MLton