The programmer knows exactly what queries calls where done in order, the 'results' provide the queries in the same order. There is no need to extra semantic
From: Florian Bösch <email@example.com>
Date: Friday, April 12, 2013 11:01 AM
To: Rémi Arnaud <firstname.lastname@example.org>
Cc: Rémi Arnaud <email@example.com>, Ben Vanik <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Kenneth Russell <email@example.com>, Gregg Tavares <firstname.lastname@example.org>, Public Webgl <email@example.com>, Brian Cornell <firstname.lastname@example.org>, Glenn Maynard <email@example.com>
Subject: Re: [Public WebGL] For review: ANGLE_timer_query extension
On Fri, Apr 12, 2013 at 7:41 PM, Arnaud, Remi <Remi.Arnaud@amd.com> wrote:
Users won't be asking for results before they're available because that's a stupid behavior. The whole spinloop of death debate is strawman. You can abuse any API. Stop inventing problems. Spinloop of death is 1) stupid 2) you won't do it because it'll kill your performance 3) the API doesn't encourage it either way 4) the documentation doesn't encourage.
Which is useless because obtaining a query and sticking it somewhere gives it meaning to the application code. A flat list of gunk doesn't have any meaning anymore, therefore useless.
It takes control away because it hides the queries.
You have not read my examples. You also have not read Bens answer to my question on the reusability of queries. You won't need to allocate them every frame. Some people might want to use pools. Others might want to use their own data structures to put them in. Stop inventing a semantic that makes this impossible.
It does not. You're just dumping a flat list on a user without any semantic meaning of where a query was used. That's useless.
Sets are useless.