[MLton-user] doc update
Vesa Karvonen
vesa.a.j.k at gmail.com
Fri Nov 23 06:38:08 PST 2007
Hi,
I cc'd my reply also to the MLton Users list.
The page http://mlton.org/MLBasisAnnotations has some documentation on
annotations.
I believe deadCode does aggressive dead code elimination silently, see
http://mlton.org/DeadCode . It should probably be listed as an expert
annotation.
-Vesa Karvonen
On Nov 23, 2007 3:06 PM, Sean McLaughlin <seanmcl at gmail.com> wrote:
> Hi Vesa,
>
> Some of those look interesting. I caught some nasty bugs with
> warnUnused. Is there documentation for these. For instance,
> does [deadCode true] mean MLton will point out what gets marked
> as dead code by the compiler, or just silently do dead code elimination
> where it doesn't otherwise.
>
> Sean
>
>
> On Nov 23, 2007 1:26 AM, Vesa Karvonen <vesa.a.j.k at gmail.com> wrote:
> > On Nov 22, 2007 3:38 PM, Sean McLaughlin <seanmcl at gmail.com> wrote:
> > > Oh, I'm sorry! I got the [annotation] syntax wrong. I was using "error" instead
> > > of "default"
> >
> > BTW, you can see the available annotations and their syntax using the
> > '-show anns' switch:
> >
> > $ mlton -show anns
> > allowFFI {false|true}
> > allowOverload {false|true}
> > deadCode {false|true}
> > forceUsed
> > nonexhaustiveExnMatch {default|ignore}
> > nonexhaustiveMatch {warn|ignore|error}
> > redundantMatch {warn|ignore|error}
> > sequenceNonUnit {ignore|error|warn}
> > warnUnused {false|true}
> >
> > With the switch -expert true, you can see a few more expert annotations.
> >
> > -Vesa Karvonen
More information about the MLton-user
mailing list