-
Notifications
You must be signed in to change notification settings - Fork 99
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
functor gem extraction #167
Comments
Actually I have been considering this for Functor too. I even started to do it some time ago (see Functor), but came across a few functor-dependent methods that I felt torn about --not wanting to remove them from facets. Can't recall off-hand what they were, but How about we do this. Lets compile a list of all the methods that depend on Functor, and then we can look them over and decide for sure. Btw, I split up Facets once before. It was very hard. But out of the split up I got some reasonably successful projects, such as Hashery, ANSI and Radix, plus a few less notable projects such as Instance, Platypus and Mixers. So I am not against the idea of spinning things off, it just has to be very clear cut and able to stand on it's own. Keep in mind though, by it's very nature Facets is going to be on the large side. it is a collection after all. But I think I've managed to keep her pretty tight despite that. I mean, I have had plenty of people dump dozens upon dozens of methods in my lap that they they wanted to see included in facets and I've had to meticulously weed through and decide which are worthy, and most do not make the cut. Even so I fully expect there are at least a few methods in there that could be trimmed to further tighten her up. |
|
So what do you think? Should all of those methods be removed from facets and put in a functor gem? If so how would that gem be organized -- same as facets, e.g. |
Could we put it in something like a facets-plus which would be to contain methods that do have some external dependency. facets-plus could include the original facets, and we could setup the api to be identical regardless of which set you have installed? |
I'd rather just have the separate functor project. I did some work on it today. I'm thinking for now Facets can just depend on functor gem for the Functor class. Later on we can worry about whether to remove the methods from facets or not (and if so add a deprecation warning for a while to give people a heads up). |
works for me. Let me know if you want anything done for that otherwise I'll plug away at the tests and demos |
I think the functor and all it's attendant pieces and parts should be extracted into a separate gem.
I've been making a start at updating the tests and qed demos of facets. Right now I think all of the following are true:
functor get lost in the shuffle. Effort is required to get there.
The text was updated successfully, but these errors were encountered: