Please change the name Lassi Kortela (21 Oct 2022 11:12 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 11:54 UTC)
Re: Please change the name Lassi Kortela (21 Oct 2022 13:03 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 13:16 UTC)
Re: Please change the name Lassi Kortela (21 Oct 2022 14:31 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 15:00 UTC)
Re: Please change the name Lassi Kortela (21 Oct 2022 16:25 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 17:43 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 18:10 UTC)
Re: Please change the name Lassi Kortela (21 Oct 2022 22:32 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (22 Oct 2022 08:03 UTC)
Re: Please change the name Lassi Kortela (22 Oct 2022 11:30 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (22 Oct 2022 11:39 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (22 Oct 2022 11:53 UTC)
Re: Please change the name Marc Feeley (22 Oct 2022 12:19 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (22 Oct 2022 12:29 UTC)
Re: Please change the name Lassi Kortela (22 Oct 2022 13:17 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (22 Oct 2022 13:26 UTC)
Re: Please change the name Marc Feeley (21 Oct 2022 13:17 UTC)
Re: Please change the name Marc Nieper-Wißkirchen (21 Oct 2022 13:26 UTC)

Re: Please change the name Lassi Kortela 22 Oct 2022 13:17 UTC

>> While “independently” is a much better name than “perform”, I think it is still not quite right.  If the evaluations are truly independent then they could be evaluated in parallel (at least in some interpretation of “independent”).  Why not simply call it “out-of-order”?

"in-any-order" would be more precise, as in-order execution is also a
permitted strategy.

I also slightly prefer "independently", as it sounds more natural since
it's one word. The thesaurus doesn't give any other good one-word names.

IMHO the following language suggested by Göran is the right thing:

   Although the order of evaluation is otherwise unspecified, the effect
   of any concurrent evaluation of the operator and operand expressions
   is constrained to be consistent with some sequential order of
   evaluation. The order of evaluation may be chosen differently for each
   procedure call.

> Each expression can evaluate to zero or more than one value.  An
> expression standing for a procedure argument must evaluate to exactly
> one value.

Yes, to account for Scheme implementations like Chibi that emulate
multiple values using a list.