Several doc pages show bits that should clearly not be there. For instance : In https://ruby-doc.org/stdlib-3.0.0/libdoc/csv/rdoc/CSV.html you can read ``` frozen_string_literal: true frozen_string_literal: true ``` In h...akim (Akim Demaille)
Sorry not to be able to provide a fix, but the documentation of strscan.c reads (https://github.com/ruby/ruby/blob/b5de66e13278ec588cbc8b76b7212e22898e6a89/ext/strscan/strscan.c#L1552): * === Match Data * * - #matched * - #matc...akim (Akim Demaille)
Ok. Well, my personal opinion is that just to have some fancy way to handle version strings, ranges of strings have inconsistent semantics. With to_a, they behave like their natural order is shortlex on some imaginary alphabet: ``` ...akim (Akim Demaille)
Hi, In Ruby up to 2.6 both `("1".."12").include?("6")` and `("1".."12") === "6"` were true. In 2.7 and 3.0, `include?` accepts `"6"`, but `===` does not. This was very handy in `case`s. Reading the documentation it is unclear to m...akim (Akim Demaille)
shyouhei (Shyouhei Urabe) wrote in #note-8: > bsarrazin (Ben Sarrazin) wrote in #note-7: > ... I disagree. Kotlin does have the feature which is the topic of this page: a null coalescing operator (https://kotlinlang.org/docs/reference...akim (Akim Demaille)
I second this proposal. Sure, it is not _needed_, we can always write things in a different way. As a matter of fact, with such an argument, hardly any improvement should be accepted. In practice when people use `||`, they do mean `??...akim (Akim Demaille)
FWIW, wrt "This is Perlish": at least one modern language has adopted a similar feature: Swift. I've used it in practice, and it is really nice to use. This page has a running example expressed in different ways: https://docs.swift.o...akim (Akim Demaille)
akim (Akim Demaille)02:04 PM Ruby Bug #17654 (Third Party's Issue): doc: trailing comments