I don't think this is necessary. It's better to keep different aspects of a calculation separate by using separate methods (building blocks) and combining them to achieve a goal. As an example, your ```a.permutation(*1..3).to_a``` can ...duerst (Martin Dürst)
@ima1zumi Not sure this is even allowed, but I'm sure I'm responsible for this behavior, and want to fix it myself, so I change the Assignee to myself.duerst (Martin Dürst)
Using 12pm for noon is indeed bad practice. Using 12am for midnight is even worse practice, because without context it's unclear whether it's at the beginning or the end of a certain date. But it is practice, at least in certain parts...duerst (Martin Dürst)
I strongly support this proposal. It would avoid a lot of confusion down the line. Ideally, we would use a term that makes it clear that this is something much more wide-reaching, and something that's supposed to be much more rarely used...duerst (Martin Dürst)
You say "queries that might find this pattern". That seems to say that you haven't found it yet. What's the result for "Hello".ensure_suffix("o!") Is it "Helloo!", or is it "Hello!"?duerst (Martin Dürst)
Unicode 17.0 is currently in alpha. Beta is planned for late May, release for September 2025. We just updated to Unicode 16.0, so we can start testing with alpha/beta.duerst (Martin Dürst)
northeastprince (Matt Almeida) wrote: > One of Ruby's core tenants is beautiful code - and a key part of that is sweating the names. Adding `it` as a pointer to the first block parameter was a huge step forward in that regard, but we're...duerst (Martin Dürst)