dsferreira (Daniel Ferreira) wrote: > > I guess that this is usually a bad idea, but it depends on what you are using your tests for. When I have to develop a complex module I usually follow TDD because TDD is a design tool for me, no...grzesiek (Grzegorz Bizon)
Thank you for your replies Daniel, Robert! > Also I only test the API. I don't unit test internal modules or classes. I guess that this is usually a bad idea, but it depends on what you are using your tests for. When I have to deve...grzesiek (Grzegorz Bizon)
While one of the core principles of Ruby is to extend the language in a way it is a most useful and convenient tool that a software developer can have in their toolbox, lack of a first-class isolation on module level can cause some serio...grzesiek (Grzegorz Bizon)
Hi again ! I've made new attempt to create nil conditional operator (https://github.com/nil-conditional). This is Ruby implementation, you can check it out here: https://github.com/grzesiek/nil-conditional/blob/master/lib/nil_conditio...grzesiek (Grzegorz Bizon)
@Recursive Madman - *try* is not native function. It is Active Support Core Extension. Moreover implementation and behavior of try is not stable (is changing depending on Rails version), it will not work when creating train wrecks an...grzesiek (Grzegorz Bizon)
Hi Nobuyoshi, thanks for reply ! Yes, this Nil Conditional Operator has to introduce new syntax. That is why this cannot be achieved via gem. Currently - of course - double question mark *??* violates syntax (in some cases) or is trea...grzesiek (Grzegorz Bizon)
Hi everyone ! Some time ago I was thinking about Nil Conditional Operator in Ruby (`??`). This would be particularly useful to avoid frequent checking for nil, and should behave and look like Null Conditional Operator introduced in C#...grzesiek (Grzegorz Bizon)
grzesiek (Grzegorz Bizon)09:13 AM Ruby Feature #14758: Add a first-class support for isolated bounded packages / modules / contexts