1. 29 May, 2018 1 commit
  2. 28 May, 2018 1 commit
  3. 19 May, 2018 1 commit
  4. 10 May, 2018 1 commit
  5. 29 Apr, 2018 2 commits
  6. 19 Apr, 2018 1 commit
  7. 18 Apr, 2018 2 commits
  8. 17 Apr, 2018 2 commits
  9. 12 Apr, 2018 1 commit
  10. 10 Apr, 2018 1 commit
  11. 06 Apr, 2018 1 commit
    • Jordan Petridis's avatar
      Remove Futures_Cpupool. · 14a90e71
      Jordan Petridis authored
      The performance boost is not good enough to justify the
      code complexity it add and the memory overhead of
      yeat another threadpool.
      
      We will start refactoring the whole pipeline implemantation
      and might transition to either rayon-futures or tokio-runtime.
      14a90e71
  12. 05 Apr, 2018 1 commit
  13. 03 Apr, 2018 5 commits
  14. 30 Mar, 2018 1 commit
  15. 19 Mar, 2018 1 commit
  16. 14 Mar, 2018 1 commit
  17. 12 Mar, 2018 1 commit
  18. 20 Feb, 2018 1 commit
  19. 10 Feb, 2018 1 commit
    • Jordan Petridis's avatar
      EpisdoeWidget: Use take_mut crate to allow for a better api. · 3a9a2f40
      Jordan Petridis authored
      Currently it's required that you take mut self in order to manipulate
      the internal state machines. This would not allow passing an Arc/Rc to
      a callback since A/Rc<T> only derefs to &T and not T.
      
      The take_mut crate allows the retrieval of ownership if you have a &mut refference
      and as long you return T again. So Arc<Mutex<Machine> could work with
      callbacks and embed Nested state machies without copying.
      3a9a2f40
  20. 08 Feb, 2018 1 commit
  21. 04 Feb, 2018 3 commits
  22. 27 Jan, 2018 3 commits
  23. 23 Jan, 2018 1 commit
  24. 22 Jan, 2018 2 commits
  25. 21 Jan, 2018 1 commit
  26. 20 Jan, 2018 1 commit
  27. 19 Jan, 2018 1 commit
  28. 18 Jan, 2018 1 commit
    • Jordan Petridis's avatar
      1.21 Gigawatts. Remove non-future indexing loop. · 93372a30
      Jordan Petridis authored
      Tried to have a seperate futures loop but it's too confusign having
      too write a Trait2, functon2, etc version of everything and keep it together.
      
      Futures are functional sort of, so the synchronous versioun can be removed.
      It still needs a ton of work though to be ready, or even get near the perf
      of of the sync+rayon version.
      93372a30