@mame I did, I apologise for not making it clear, I'm reiterating it to add weight to the con, its not just a simple "it is somewhat fragile, it may refer to a wrong variable" its a "this shadows the most commonly used method in the most...JonRowe (Jon Rowe)
Its worth pointing out that this would always have to be lower priority than methods and other such locals defined in order to allow code to work. If precedence for this was changed to later override existing definitions of it, or simply...JonRowe (Jon Rowe)
> Is that used in practice though? I know pending examples, but I would expect they at least have a description. No but as Ruby doesn't allow method overloading you do create that ambiguity, and the possibility for future bugs due to ...JonRowe (Jon Rowe)
👋Hello! As the current maintainer of RSpec I'm concerned about the confusion here. ```ruby RSpec.describe do it "will do the thing" do it # now refers to the first argument to the block? (Which ironically is the example itsel...JonRowe (Jon Rowe)
> These days many people specify versions in Gemfile like gem "some-libs", "< 2". > ... More people use `gem "some-libs", "~> 2.0.0"` and having breaking changes in a minor or patch release break the applications dependant on them. T...JonRowe (Jon Rowe)
I tried to work around this bug by duplicating the proc with `.dup` but it seems that dup doesn't actually duplicate the proc. So I went digging through the C code and discovered that `define_method` actually does try to dup the proc wit...JonRowe (Jon Rowe)
This seems odd behaviour, given that in normal usage you'd never be able to satisfy the constraint to avoid the ArgumentError, I feel this should return false like a proc would do.JonRowe (Jon Rowe)
@wardrop The reason we all love Ruby is because it makes us happy. This suggestion makes me unhappy, so I'm saying so, and I'm attempting to do so constructively. Ruby has an ethos around writing elegant clean code which deserves protect...JonRowe (Jon Rowe)
Although this is just my 2¢... I think this is a bad idea... and here's why... 1) One of the principles of good software development is "tell don't ask", meaning that we should be passing messages around objects, telling others to do t...JonRowe (Jon Rowe)