Guillaume Malette
Guillaume Malette
> You fixed that by changing the behaviour of `assert` when a block is passed, not by changing the style guide. Given **all** methods implicitly accept blocks and would present...
To be clear, I consider the changes to the `assert` method in https://github.com/Shopify/shopify/pull/179085 to be stopgap measures. They're not a fix in any way and I think it's nonsense to...
> Ruby developers in my experience assume a method _will not_ properly handle a block unless it's specifically designed to use one or they've verified it does I don't think...
Since there are no macros (it's just method calls) nor DSL (it's just Ruby) in Ruby , can you clarify what you mean by those please?
I don't know if there is a practical difference in MRI, but VMs will typically be able to optimize the `raise Class, msg` more easily
> I would expect any subclass of Exception to be able to receive new with an optional error message That's not an expectation that the Ruby's core lib fulfills; some...
I'm worried a future `Predicate` type could be introduced with `test(object)` method, which would be excluded. Perhaps we could ignore it only in the `test` folder? It would probably require...
> Since we are here for test, how about the RSpec methods (spec, describe, context, subject etc)? For the methods which are not typically used elsewhere I wouldn't have a...
Depends what we do with #106
> I'm finally looking into this as I (also) might need to introduce an `AnyAdcPin` Until this happens, how does one create an array of ADCPins on the same ADC?...