split-items-ready-to-load reorders reads in the outgoing remote transaction

[awkay]

The function puts the items to load in a set, which will often cause them to reorder. This may cause post-mutations to run in an order that the user would not expect. This could cause dependent reads to be missing data on post mutation.

[awkay]

I sent a patch for this, but it did not fix an in-the-field report

[tobiasquinn]

Simple test case https://github.com/tobiasquinn/untangled-template/tree/issue-67-test-case
Print output from "TEST" button is 3,2,1 expect output 1,2,3