domenic at domenicdenicola.com (2013-12-10T01:28:36.520Z)
On 12/02/2013 09:13 AM, Allen Wirfs-Brock wrote:
> Jason suggests keeping the token stream and backing up. Another alternative is remembering the source position of the start of the parameter list and reparsing when the ambiguity and strictness is resolved. Whether text, token, or AST based reprocessing is better is an implementation decision.
It does matter whether it's re-parsed or re-lexed, and there lie sleeping dragons. From the other thread that was exploring the =>* extension that would wake one up:
> ```js
> (a = yield/"/g, b = yield/"/g) =>* {}
> ```
>
> Does this generator have one or two parameters?
On 12/02/2013 09:13 AM, Allen Wirfs-Brock wrote: > Jason suggests keeping the token stream and backing up. Another alternative is remembering the source position of the start of the parameter list and reparsing when the ambiguity and strictness is resolved. Whether text, token, or AST based reprocessing is better is an implementation decision. It does matter whether it's re-parsed or re-lexed, and there lie sleeping dragons. From the other thread that was exploring the =>* extension that would wake one up: > (a = yield/"/g, b = yield/"/g) =>* {} > > Does this generator have one or two parameters? Waldemar