First, I would like to thank mame for the explanation in regards to the namespace discussion, or rather the pre-discussion in regards to design decision(s). Probably not everyone knew about the prior discussion(s), so it seems useful to ...rubyFeedback (robert heiler)
Today I was updating / porting some legacy code, to ruby 3.4.1. Ruby 3.4.1 changed a few things, including some warnings, which is actually quite useful in the long run, in my opinion - although right now requiring some changes, whi...rubyFeedback (robert heiler)
MaxLap wrote: > Which I hope no one writes For instance, at: foo&.empty?&.! I would not write that myself because I do not use "&.". I understand that other people use it but to me it feels at odds with other syntax of r...rubyFeedback (robert heiler)
Personally I do not think I would need this feature (I share mame's opinion here), but what has not yet been pointed out is the language streem by matz (https://github.com/matz/streem). Now, streem is not ruby and matz has not pushed str...rubyFeedback (robert heiler)
Personally I find the double ... rather confusing. I understand the benefit of a more succint syntax - e. g. eliminating "(*args, **kwargs, &block)" - but even then I find the dual-triple-dot very strange. It seems rather "un-ruby" to me...rubyFeedback (robert heiler)
> ruby -run is one of cool feature of Ruby. Should we avoid uninstalling un gem? I think -run is kind of neat; it's a bit like a mini-DSL for the commandline. (Having said that, I actually do not use it myself; I instead use a cust...rubyFeedback (robert heiler)
Not so sure about these names. Note that get_and_set() may have people wonder why it is not set_and_get(). :D In regards to .update_value() people could ask why the old value is returned rather than the new one. I guess **exchange_valu...rubyFeedback (robert heiler)
I just noticed that it actually already reported that a semicolon is missing: "expected a newline or semicolon" So I would like to reword the above to perhaps consider also showing this information in the raised message below: ack...rubyFeedback (robert heiler)
So this is not quite a bug, but I thought it may fit better here, as it is neither a feature, and also not quite fitting under misc. Before I will explain the issue, let me copy/paste the code I use so that others can reproduce what I...rubyFeedback (robert heiler)
I don't have any pro or con opinion on the feature itself; in regards to ^foo versus =foo, I think users may wonder about both: ^ specifically because many regexes may have it, such as /^foobar/, and with = they may assume some assignme...rubyFeedback (robert heiler)