Initial sketch-out (broken)
Sequencer working so imports are always processed in the same order
when finding variables, look inside sub import nodes
make sure an error is not lost
flatten import visitor so that variable imports can be processed at the end of a global queue
Tidy Import Visitor arguments
Tidy context stack into actual stack - no need for an array
Refactor out the processing of the import, ready to be done asyncronously
Method for how it will work asyncronously (broken)
test for final working
Fix - for some reason the flattening done by the import visitor is required
sequencer logic for variable import
use structure to run variable imports last
further test case
Merge pull request #2246 from less/import-sequence

Attempt to fix import sequencing