I found 130 (5 sets of 26 alphabets) characters matching both `\p{S}` and `\p{Word}`. The visual looks like alphabet-ish symbol character ~~~ruby (0..0x10ffff).select{(s=''<<it; s=~/\p{Word}/&&s=~/\p{S}/) rescue false}.map{''<<it}.joi...tompng (tomoya ishida)
In RDoc, comment that starts with "##" is a metaprogramming method definition. If it's not a metaprogramming method definition, "##" shouldn't be used. https://github.com/ruby/rubygems/commit/b1953a3a09tompng (tomoya ishida)
> Isn't it impossible? To match, regexp needs to satisfy negative lookahead, so there should not be anything to capture. As you wrote, captures are not available OUTSIDE of negative lookahead and also in MatchData. But in `/(?!([a-z]...tompng (tomoya ishida)
First issue > This should be false in both cases. I think `Regexp.linear_time?(/(?<=(a))/)` matches in linear time. If the issue is just for inconsistency between lookahead and lookbehind, it's not a bug. Here's an example: ~...tompng (tomoya ishida)
* Bundle rbs-3.10.0.pre.1 * Update rbs gem entry with commit hash Updated rbs entry to include commit hash. * Fix rbs entry in bundled_gems * Update rbs gem to version 3.10.0.pre.2 Updated rbs gem version from 3.10.0.pre.1 to 3.10.0...tompng (tomoya ishida)
Except the problematic case `-> { }`, start position consistently excludes whitespaces just after `->`. So I think `-> { }`'s source location should be `{ }`. ~~~ruby -> ( ) { }.source_location # ["(irb)", 1, 3, 1, 10] ^^^^^^^ ->...tompng (tomoya ishida)
tompng (tomoya ishida)07:00 PM Ruby Bug #21870: Regexp: Warnings when using slightly overlapping \p{...} classes