Stream: t-compiler

Topic: forcing queries


Zoxc (Feb 17 2019 at 05:03, on Zulip):

When forcing queries, how do we ensure that the query would run at the same time for a clean build? Or if we manage to make queries order independent, how do we ensure that the query would run at all?

cc @mw

mw (Feb 19 2019 at 10:39, on Zulip):

I'm not sure I follow

mw (Feb 19 2019 at 10:40, on Zulip):

try-mark-green will mark and re-execute things in the order they were recorded during the previous session

mw (Feb 19 2019 at 10:41, on Zulip):

is that what you mean?

Zoxc (Feb 19 2019 at 10:46, on Zulip):

Dependencies of the current session may be different from the dependencies from the previous one. We may execute queries we wouldn't otherwise do

Zoxc (Feb 19 2019 at 11:01, on Zulip):

Maybe executing queries in order and stopping at the first red one takes care of this? Because we'd need to execute a query in order to gain information we can branch on.

Zoxc (Feb 19 2019 at 11:21, on Zulip):

So we can't execute queries after the first red one. The information from the red query could be used to change which later queries we would execute.

mw (Feb 19 2019 at 12:28, on Zulip):

Yes, we have to stop a the first red dependency - otherwise we'd run into trouble

mw (Feb 19 2019 at 12:28, on Zulip):

an early implementation of incr. comp. didn't observe this kind of order (we had hash sets of dependencies) but it ran into problems immediately

Zoxc (Feb 19 2019 at 12:29, on Zulip):

I though we did that only because our queries can't currently run in an arbitrary order

mw (Feb 19 2019 at 12:32, on Zulip):

I think they can pretty much run in any order, only red-green marking has to take care not to invoke queries that don't make any sense anymore in the new session

mw (Feb 19 2019 at 12:33, on Zulip):

well, at least in theory they should be able to run in any order :)

Last update: Nov 22 2019 at 05:50UTC