HaloO,
Larry Wall wrote:
That is, coro and loop tend to violate single-assignment semantics, and
single-assignment semantics are easier to map into functional semantics.
So if we do allow coro in Perl 6, it'll probably be a second-class
citizen like loop and goto and die (and anything else considered
harmful but useful). But I don't see much use for it offhand.
Does that imply that multiple assignment is second-class, too?
And that with a language that provides the concept of eternal
equality with ===, or checking of referential identity with =:=.
Big surprise that is.
Regards, TSa.
--
"The unavoidable price of reliability is simplicity"
-- C.A.R. Hoare
