John Snow writes:
> On 4/27/21 9:47 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 4/23/21 11:46 AM, Markus Armbruster wrote:
John Snow writes:
> The short-ish version of what motivates this patch is:
>
> - The parser initializer does not possess adequate con
On 4/27/21 9:47 AM, Markus Armbruster wrote:
John Snow writes:
On 4/23/21 11:46 AM, Markus Armbruster wrote:
John Snow writes:
The short-ish version of what motivates this patch is:
- The parser initializer does not possess adequate context to write a
good error message -- It tries to
John Snow writes:
> On 4/23/21 11:46 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> The short-ish version of what motivates this patch is:
>>>
>>> - The parser initializer does not possess adequate context to write a
>>>good error message -- It tries to determine the caller's sema
On 4/23/21 11:46 AM, Markus Armbruster wrote:
John Snow writes:
The short-ish version of what motivates this patch is:
- The parser initializer does not possess adequate context to write a
good error message -- It tries to determine the caller's semantic
context.
I'm not sure I get wh
John Snow writes:
> The short-ish version of what motivates this patch is:
>
> - The parser initializer does not possess adequate context to write a
> good error message -- It tries to determine the caller's semantic
> context.
I'm not sure I get what you're trying to say here.
> - We don't
The short-ish version of what motivates this patch is:
- The parser initializer does not possess adequate context to write a
good error message -- It tries to determine the caller's semantic
context.
- We don't want to allow QAPISourceInfo(None, None, None) to exist.
- Errors made using such a
