| Age | Commit message (Collapse) | Author |
|---|
|
Since https://github.com/ruby/ruby/pull/15212 these are proper syntax
errors, so no need to handle this explicitly anymore.
Also updated the example in the docs for this
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12955
|
|
The inspect format was intentionally changed as an outcome of
[Bug #20433] [ruby-core:118668], but some documentation update
was missing, as [Bug #20962] pointed out. Update some output
examples that clearly use Hash#inspect.
Notes:
Merged: https://github.com/ruby/ruby/pull/12384
Merged-By: XrXr
|
|
Guard clauses can only be used in `case` pattern matching statements,
not in `=>`/`in` operators.
|
|
* Remove section about experimental status
* Add references to core objects that can deconstruct
Notes:
Merged: https://github.com/ruby/ruby/pull/7316
|
|
|
|
https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20210715Japan.md#feature-17724-make-the-pin-operator-support-instanceclassglobal-variables-jeremyevans0
|
|
Pin matching for local variables and constants is already supported,
and it is fairly simple to add support for these variable types.
Note that pin matching for method calls is still not supported
without wrapping in parentheses (pin expressions). I think that's
for the best as method calls are far more complex (arguments/blocks).
Implements [Feature #17724]
Notes:
Merged: https://github.com/ruby/ruby/pull/4502
|
|
This commit is based on the patch by @nobu.
|
|
|
|
Thanks to @zverok for the report.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2952
|
|
Add separate doc/syntax/pattern_matching.rdoc, add
link to control_expressions.rdoc.
The documentation is "reverse-engineered" from Ruby 2.7
behavior and early preview presentations, and corrected
by pattern-matching feature author @k-tsj.
Notes:
Merged: https://github.com/ruby/ruby/pull/2786
|
