From: "tenderlovemaking (Aaron Patterson) via ruby-core" Date: 2023-09-28T19:55:21+00:00 Subject: [ruby-core:114914] [Ruby master Feature#19904] Deprecate or warn on multiple regular expression encodings Issue #19904 has been updated by tenderlovemaking (Aaron Patterson). mame (Yusuke Endoh) wrote in #note-1: > I think it's a good idea, but am curious as to what (if any) led you to want to prohibit this. > Did you get in trouble because of this? Or did you just notice it (while implementing Prism or something)? No, it didn't cause any trouble. @eileencodes and I just noticed this while implementing regular expression support with Prism. ---------------------------------------- Feature #19904: Deprecate or warn on multiple regular expression encodings https://bugs.ruby-lang.org/issues/19904#change-104783 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Priority: Normal ---------------------------------------- It seems like you can pass multiple encoding flags to regular expression literals, but I think this should be a warning or possibly syntax error. For example: ```ruby x = /foo/nu p x.encoding ``` `n` says the RE should be ASCII-8BIT, and `u` says it should be UTF-8. The last flag wins, so in this case the regular expression gets UTF-8 encoding. However, I think it should be a warning or even a syntax error if you specify multiple encoding options on a regular expression. It seems like a mistake if programmers specify multiple. Thanks! -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/