Fixing breaking change to Concurrent::Future in Crystal 0.35

[konung]

1. Crystal team has move Concurrent::Future to community-future shard, and remove functionality from standard library in Crystal version 0.35
2. Discussion is here: Drop Concurrent::Future and top-level methods delay, future, lazy crystal-lang/crystal#9093
3. This update lucky-cluster to be compatible with the change

On a side note, Amber::Cluster actually spawns separate processes via Process.fork - worth looking into.

[konung]

There are no specs to run so it fails, but I added to luckyframework-website on my mac just to test, and it works as expected.

[konung]

Screenshot of luckyframework website runing wiht MAX_THREADS=16

There is no measurable difference on Mac. But per your comment in Readme, it sounds like I need to try this on Linux

[jwoertink]

Awesome! Thanks for the update. This all looks good to me. Yeah, I saw how Amber was handling this, but this method was based off spider-gazelle. Might be worth checking in to again later. Thanks for the heads up.