Iain Sandoe <i...@sandoe.co.uk> writes:
>> static tree
>> get_awaitable_var (suspend_point_kind suspend_kind, tree v_type)
>> {
>> - static int awn = 0;
>> + auto cinfo = get_coroutine_info (current_function_decl);
>> + gcc_assert (cinfo);
>
> If the purpose of this is to check for mistakes during development (i.e. we do
> not see a reason for having it in a released compiler) - then it’s better to
> use
> gcc_checking_assert() which will disappear for non-checking builds.I figured it was OK since this check is extremely light - I can use gcc_checking_assert if you prefer. No strong feelings in this instance. Thanks. -- Arsen Arsenović
signature.asc
Description: PGP signature
