mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

I lied; ObjC 2.0 did not actually pick up CLU/Sather iterators. They've been dormant since the 90s. Sigh.

Browse Source
This commit is contained in:
Graydon Hoare 2010-07-01 09:37:06 -07:00
parent 0bc1ad60ef
commit 8bf6ae99f4
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/rust.texi
View File

@ -2811,14 +2811,14 @@ current iterator, suspends execution of the current iterator, and transfers
control to the current put-recipient frame.
A @code{put} statement is only valid within an iterator. @footnote{A
@code{put} statement is analogous to a @code{yield} statement in the CLU,
Sather and Objective C 2.0 languages, or in more recent languages providing a
``generator'' facility, such as Python, Javascript or C#. Like the generators
of CLU, Sather and Objective C 2.0, but @emph{unlike} these later languages,
Rust's iterators reside on the stack and obey a strict stack discipline.} The
current put-recipient will eventually resume the suspended iterator containing
the @code{put} statement, either continuing execution after the @code{put}
statement, or terminating its execution and destroying the iterator frame.
@code{put} statement is analogous to a @code{yield} statement in the CLU, and
Sather languages, or in more recent languages providing a ``generator''
facility, such as Python, Javascript or C#. Like the generators of CLU and
Sather but @emph{unlike} these later languages, Rust's iterators reside on the
stack and obey a strict stack discipline.} The current put-recipient will
eventually resume the suspended iterator containing the @code{put} statement,
either continuing execution after the @code{put} statement, or terminating its
execution and destroying the iterator frame.
@page