> On 15 Sep 2021, at 20:50, Jason Merrill wrote:
> On 9/15/21 14:32, Iain Sandoe wrote:
>> Hi Jason,
>>> On 15 Sep 2021, at 18:32, Jason Merrill wrote:
>>>
>>> On 9/14/21 11:36, Iain Sandoe wrote:
Hi
Some small code cleanups that allow us to have just one place that
we handle a s
On 9/15/21 14:32, Iain Sandoe wrote:
Hi Jason,
On 15 Sep 2021, at 18:32, Jason Merrill wrote:
On 9/14/21 11:36, Iain Sandoe wrote:
Hi
Some small code cleanups that allow us to have just one place that
we handle a statement with await expression(s) embedded. Also we
can reduce the work done
Hi Jason,
> On 15 Sep 2021, at 18:32, Jason Merrill wrote:
>
> On 9/14/21 11:36, Iain Sandoe wrote:
>> Hi
>> Some small code cleanups that allow us to have just one place that
>> we handle a statement with await expression(s) embedded. Also we
>> can reduce the work done to figure out whether a
On 9/14/21 11:36, Iain Sandoe wrote:
Hi
Some small code cleanups that allow us to have just one place that
we handle a statement with await expression(s) embedded. Also we
can reduce the work done to figure out whether a statement contains
any such expressions.
tested on x86_64,powerpc64le-lin
Hi
Some small code cleanups that allow us to have just one place that
we handle a statement with await expression(s) embedded. Also we
can reduce the work done to figure out whether a statement contains
any such expressions.
tested on x86_64,powerpc64le-linux x86_64-darwin
OK for master?
thanks
Hi,
This is a small code cleanup patch, but is useful in follow-on work to
fix actual bugs - by making it only one place that we need to consider
the flattening of a statement containing await expressions.
tested on x86-64, powerpc-linux, x86_64-darwin,
OK for master?
thanks
Iain
— commit me
