4 Commits

Author	SHA1	Message	Date
Aralox	7022db1bf6	Modify async for test to avoid known try-except problem with trailing unnecessary continue when the try-except is not followed by any other statements. ... Add an xfail test to capture this failing scenario.	2020-10-22 15:35:59 +11:00
Aralox	e80aa996fa	Only initialize the async for once.	2020-10-22 09:11:51 +11:00
Aralox	91a23f914d	Implement better handling for async for. ... Instead of ignoring boilerplate when decompiling `async for`, build the loop semantically by deconstructing the BLK_WHILE -> BLK_CONTAINER -> BLK_TRY that python generates when compiling an `async for` (see https://www.python.org/dev/peps/pep-0492/#asynchronous-iterators-and-async-for). When reading GET_AITER, convert the BLK_WHILE into a BLK_ASYNCFOR in the same way as a `for` loop. Ignore GET_ANEXT. Use END_FINALLY as the trigger to finish building the BLK_ASYNCFOR: -> Extract the loop variable from the contents of the BLK_TRY. -> Throw away the BLK_TRY and BLK_CONTAINER, leave the BLK_ASYNCFOR on top of the stack.	2020-10-21 19:32:20 +11:00
Aralox	8933c9a4a9	Add support for async for. Issue #124 ... Ignore 'boilerplate' opcodes that set up the async iteration logic internally (https://www.python.org/dev/peps/pep-0492/#asynchronous-iterators-and-async-for) - We don’t need any of this as GET_AITER is enough to tell us that we are in an `async for`.	2020-10-20 20:39:23 +11:00