From: "palkan (Vladimir Dementyev)" Date: 2022-01-11T10:39:00+00:00 Subject: [ruby-core:107050] [Ruby master Feature#18408] Allow pattern match to set instance variables Issue #18408 has been updated by palkan (Vladimir Dementyev). palkan (Vladimir Dementyev) wrote in #note-6: > jeremyevans0 (Jeremy Evans) wrote in #note-2: > > I don't think it's a bug that pattern match only supports setting local variables. However, I agree that it would be a useful feature for pattern match to support setting instance variables, especially now that you can pin instance variables in pattern match in Ruby 3.1. > > I've already implemented this feature for Ruby Next ([parser changes](https://github.com/ruby-next/parser/pull/7/files#diff-7b4b5ca5bdfd0c23eb3e07f76208b48bd81b43cf984685415abe4da84bab4efa)) and would like to work on a MRI "backport" ("forwardport" ����) if no one minds. /cc @ktsj Here is a PR: https://github.com/ruby/ruby/pull/5426 ---------------------------------------- Feature #18408: Allow pattern match to set instance variables https://bugs.ruby-lang.org/issues/18408#change-95881 * Author: Dan0042 (Daniel DeLorme) * Status: Open * Priority: Normal * Assignee: ktsj (Kazuki Tsujimoto) ---------------------------------------- I expected this to work: ```ruby 42 => @v ``` But instead it raises "syntax error, unexpected instance variable" Is this intentional? -- https://bugs.ruby-lang.org/ Unsubscribe: