Features for Anyolite 2.0.0

[Hadeweka]

Hello there,

after some feedback and own experience with Anyolite I think it's time for some (minor, but breaking) changes to improve the user experience - so it's time to talk about Anyolite 2.0.

Currently planned are:

Reworking the installing process

In Anyolite 1, the shards is installed via shards. All C bindings and libraries are then processed using the postinstall option, but there are some scenarios where this isn't desirable (especially if you want to bind against your own Ruby library).

Therefore, Anyolite 2 will NOT install its dependencies when running shards. Instead, the user has to call the build script manually. This adds an additional step to anyone using Anyolite - but it adds more freedom to the build process overall.

The build script will probably still be a Rake script (since mruby requires Rake anyway), but due to the independence to shards, additional options can be included easily.

Setting some previously optional features to default

Due to the way Anyolite worked in its earliest versions, non-keyword arguments were the default argument type for any function arguments - even for optional arguments. This is not intuitive, but changing the default would break programs using earlier Anyolite versions.

A workaround was introduced using the ANYOLITE_DEFAULT_OPTIONAL_ARGS_TO_KEYWORD_ARGS option, which defaults optional arguments to keyword arguments, but this will be the default behavior in Anyolite 2.

Other features (this is where YOU come in)

Besides these changes, I would like to start this discussion about other features that might be of interest to users.
Do you have any ideas? Do you happen to not like any of the planned changes?

Feel free to dream up anything you want - for now you don't have to care about the implementation details, just state here what your ideal Anyolite would look like 😃