Xavier Noria
Xavier Noria
> I believe there is a great difference between documentation statements like "Foo will do this" or "Foo will fail if ...", and examples. No, no, the examples are public...
> I appreciate your choice of a hill to die I don't like that you put it in that way, honestly. One way to not mess with unespeficied behavior is...
@jeremyevans we were writing at the same time. If the current patch is good for you, I'm fine.
@zverok one of my first comments was "I like it. It's concise and enough.". That was the end of it for me. Appreciate the clarification, in text, I could not...
> It is public contract. APIs such eval, binding.instance_variable_get etc, implies that variables stay valid until the scope is exited. It's probably in Ruby spec somewhere. Or maybe a smart...
> All I tried to say (with badly chosen idiom!) is that I see your attention to a problem of whether invoking the assumption that dynamic subclass would be produced...
This was addressed by https://github.com/seyhunak/twitter-bootstrap-rails/pull/935. I believe this issue can be closed.
@deivid-rodriguez that is fantastic, and thanks a lot for the credit ❤️.
Hi @esb while we do not actively maintain this gem, if you provide a patch that fixes the issue we will apply.
That is fine, but I'll think of a better place to put it, since it is something you won't be asked for normally.