The Crystal community has somewhat decided to use crystal as the language's topic.

To avoid fragmentation in the community, please change the crystal-language topic, that only has ~30 repositories at the moment, to crystal.

Any contributor can change it from the repo's homepage.

See crystal-lang/crystal#4241 for more context.

Thank you very much :)

I feel the spec library of crystal is really limiting. As for example I am declaring the array variable on each case, instead of having a before_each. Guess I can blame my testing background for rspec and minitest for that 😬

I suggestion https://github.com/ysbaddaden/minitest.cr as it has the features like let or we can use spec2 (https://github.com/waterlink/spec2.cr) which has stuff like random order, before for current and nested context.

Listing out the methods that is pending to be implemented. Methods information taken from ActiveSupport - core_ext

• Array#in_groups
• Array#from
• Array#to
• Array#without
• Array#wrap
• Array#

With each addition of new features the size of the single class is increasing. May I suggest we break up a class in the following format.

+-- arrays/
|   +-- grouping/
|         +-- in_groups.cr
|         +-- split.cr
|   +-- grouping.cr

So that the code will be more organised. If people want to just include the grouping of array they can do crystal_on_steroids/arrays/grouping or if the one just a specific method they can do crystal_on_steroids/arrays/grouping/in_groups.

The above require is just an added benefit the main thing is to make the code more organised as we are going to add more methods.