Make ALL completely ignore UNSET! values

[Siskin-Bot]

Submitted by: fork

Currently, ALL sort of ignores unset values. Which is to say, an UNSET! will not cause the evaluation to fail and return #[none]

>> all [10 print "Hello" 20]
Hello
== 20

However, if an unset happens at the end, that UNSET! value is returned:

>> all [10 print "Hello"]
Hello
>>

If an UNSET! is taken out of the consideration completely, that should return 10. Similarly, if all the evaluations are UNSET!, the result should be the same as an empty block (true). Today that is not the case:

>> all []
== true

>> all [print "Hello"]
Hello

---

^{Imported from: CureCode [ Version: r3 master Type: Bug Platform: All Category: Unspecified Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#2201}

Comments:

Rebolbot commented on Mar 6, 2015:

Submitted by: fork

Duplicate of #850

---

Rebolbot added the Type.bug on Jan 12, 2016

---