Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge with samvv/elixir-toolbelt #114

Open
ghost opened this issue Feb 16, 2017 · 2 comments
Open

Merge with samvv/elixir-toolbelt #114

ghost opened this issue Feb 16, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 16, 2017

Hi,

I started my own small utility belt library but shortly after discovered yours thanks to h4cc/awesome-elixir. I am currently still bootstrapping it, but would it be a good idea to merge in the future? I noticed that there already are some functions that are not there yet in this library.

Will keep you updated.

Regards,
Sam

@duijf
Copy link
Collaborator

duijf commented Feb 25, 2017

Hi Sam! Thanks for your interest! I'm definitely interested in collaborating. Any reason in particular you decided to start your own lib instead of sending PRs? (No worries about the competition, just want to know if we could have done things better)

@ghost
Copy link
Author

ghost commented Feb 26, 2017

Hey,

The most important reason was that I wanted to experiment a bit more than forking allowed me to do. I wanted to start from scratch, without being biased. For instance, I've found a pretty clean way of seamlessly extending the core modules. I wasn't sure this was a good thing to do, but now I'm starting to get convinced it really is. You just do a use Toolbelt (or use Crutches, perhaps?), and it works.

If I find a time, I'll start making pull requests. Just to be clear: would you accept a pull request for use Crutches as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant