Issue #20504 has been updated by kddnewton (Kevin Newton). I'm fine with it analyzing the string literals, I would just prefer it take the same codepath as the interpolated variable case, in which it would produce an ascii-8bit regular expression as opposed to raising an error. ---------------------------------------- Bug #20504: Interpolated string literal in regexp encoding handling https://bugs.ruby-lang.org/issues/20504#change-108463 * Author: kddnewton (Kevin Newton) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- There is some very odd behavior that I'm not sure is intentional or not, so I'm looking for guidance. In here: ```ruby # encoding: us-ascii interp = "\x80" regexp = /#{interp}/ ``` the `regexp` variable is a ascii-8bit regular expression with the byte interpolated into the middle. However, if you inline that interpolation: ```ruby # encoding: us-ascii regexp = /#{"\x80"}/ ``` you get a syntax error, saying it's an invalid multi-byte character. I'm not sure what the rule is here, as it seems inconsistent. Is this the correct behavior? I would prefer if it would create an ascii-8bit regular expression like the first example, which would be consistent. -- https://bugs.ruby-lang.org/