On 09/29/2015 02:02 AM, Markus Armbruster wrote:
While at it, we were always passing None as the location of
array types, making that parameter useless; sharing the
location (if any) of the underlying element type makes sense.
>>>
>>> The parameter is useless only because all array
Eric Blake writes:
> On 09/28/2015 06:56 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> A future patch will enable error detection in the various
>>> QapiSchema check() methods. But since all errors have to
>>> have an associated 'info'
On 09/28/2015 06:56 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> A future patch will enable error detection in the various
>> QapiSchema check() methods. But since all errors have to
>> have an associated 'info' location, we need a location to
>> be associated with
Eric Blake writes:
> A future patch will enable error detection in the various
> QapiSchema check() methods. But since all errors have to
> have an associated 'info' location, we need a location to
> be associated with all implicit types. Easiest is to reuse
> the location
A future patch will enable error detection in the various
QapiSchema check() methods. But since all errors have to
have an associated 'info' location, we need a location to
be associated with all implicit types. Easiest is to reuse
the location of the enclosing entity that includes the