Michel Belleville
Michel Belleville
I also tried another approach, changing the Monad.within method: ``` ruby def within(&block) and_then do |value| self.class.new(block.call(value)) end end ``` Which, in turn, breaks the eventually specs ^^°: ``` spec/monads/eventually_spec.rb:73...
Hi @sclinede, it's been a while so I may be fuzzy on the details, but [I submitted a pull request](https://github.com/tomstuart/monads/pull/9) to fix the thing I think was broken. What was...
Here, I added a test that showcases the problem. You can checking out commit 6e3f0e6f1910c60d98ac20791d9f639fce553f07 and run the spec to see it failing, the next commit is the fix I...
Agreed, although I don't quite see how I can make the test more obvious ^^° The alternatives I tried were actually less obvious. I'll submit the best I can think...
Well, here's another approach, with only one root and branch object. WDYT?
There it is ^^
Also agreed on my side... I think I have an idea on how to implement it without the .flatten(2) hack, I'll keep in touch.
I've tried working around it but I keep on bumping on new problems ; there's something I'm missing, and I think it has something to do with the super-class, perhaps...
Ok, I think I've had my epiphany of sorts. I've upped my PR with new code a test. Here's what went wrong if I'm actually right: ``` ruby # from...
Glad to be of service ^^ As for the: ``` ruby module Monads class Many # … def self.from_value(value) Many.new(Array(value)) end end end ``` I'm not sure how it's supposed...