Began more refactoring and discovered a potential issue where work stealing causes 'isEmpty' and dequeue returns to be non-deterministic; its possible for a node to be processed, but then steal from a node we have not processed yet and end up causing us to heaps of elements
Began more refactoring and discovered a potential issue where work stealing causes 'isEmpty' and dequeue returns to be non-deterministic; its possible for a node to be processed, but then steal from a node we have not processed yet and end up causing us to heaps of elements

LouisJenkinsCS/Distributed_Queue,LouisJenkinsCS/Distributed_Queue