Aloïs Cochard

Results 65 comments of Aloïs Cochard

@jdegoes okay, this makes sense. Thanks for explaining it clearly. I realize how important it can be for you, especially point 1. It seems that people that fear LGPLv3 are...

I'm pretty confident none of my commits include code copied from Scalaz7 (type-class definition might looks exactly the same, but this is purely incidental... those are so general anyway), also,...

I don't really see the point of a modular Prelude when you have all the trait available as currently, I mean if keep transformers and other stuff in dedicated modules...

@edmundnoble the thing, we use as much as possible resolution thru companion object, which I believe invalidate a direct comparison with this analysis. We should be careful about what we...

:+1: you can remove all of those I won't mind at all :-) makes sense

I don't see a massive advantage at using Jekyll + GitHub Pages. Hakyll is great and it's not a big deal to do the deployment locally, also if you really...

It's like with coherence: there is only one proper way to draw a Z! https://www.youtube.com/watch?v=XumDitAgl9c ![](https://static.comicvine.com/uploads/original/11120/111208964/4893337-5055759009-signe.jpg)

:+1: about not using subtyping, I have been beaten so many times by it that I don't see any benefit to use it. About the modules split, I have played...

@puffnfresh that is exactly why I created a `prelude` module in my prototype, so IList (or anything that in fact "fix" datastructure of the base library) would be there. I...

@puffnfresh BTW, just to be clear I'm not sure -as you said- if the separation does _really_ bring much in term of modularity. I have read a few time people...