I am looking at the difference in behaviour between
compose and reduce:

First, let's see the result of this either expression:

        >> type? either none [][]
        == unset!

Ok, now let's look at reduce:

        >> reduce [unset! either none [][]]
        == [unset! unset]

Why was the first unset! molded and the second formed?


Now let's look at compose:

        >> compose [(either none [][])]
        == []

I like the above compose behaviour, it is useful, but
why doesn't the following unset value also disappear?

        >> compose [(unset!)]
        == [unset!]

Anton.
-- 
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.

Reply via email to