[e-lang] Trinary-define syntax, and ejector behavior (was Re: Atomic expansion of MatchBindExpr ...)

[Mark S. Miller]

Kevin Reid wrote:
> ? int.coerce('a', def _(arg) :any { "foo" })
> # problem: optEjector <_> returned: "foo"
> 
> (this error is generated by throw#eject/2)
> 
> I believe it is sufficient, if not optimal, since an exit function (my
> term for the more general category of which ejectors are a member) which
> returns is faulty and should be fixed; after that, the actual problem
> can be found.
> 
> However, if I can find a good wording, I will certainly change this to
> include the original problem.

Yes, I think that including it would be good.

Btw, I'll be traveling and mostly unavailable until Monday May 29.

-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM