3 Commits

Author	SHA1	Message	Date
Mike Jensen	ccb6083045	Attempting to prevent interrupting threads after future has completed. ... We added a 4th state, so we have "Canceling and Canceled". We are in canceling state if we previously were running, and will not transition to canceled till after the interrupt has been sent. So at the end if we are not running, or already canceled, we will sleep, waiting for the interrupt to occur so we can be sure we handle it before we let the thread complete. This also fixes a condition where we returned true on a cancel after a task has already been canceled	2014-03-10 16:14:10 -06:00
Mike Jensen	d56087240d	Changes so that we only set the running thread if we actually ARE the running thread	2014-03-10 12:43:22 -06:00
Mike Jensen	83a31314e0	Added implementation and tests for FutureTask. ... I also was missing the set operation for AtomicReference, and cleaned a couple things up from LockSupport.	2014-03-10 10:53:49 -06:00