[#109115] [Ruby master Misc#18891] Expand tabs in C code — "k0kubun (Takashi Kokubun)" <noreply@...>

Issue #18891 has been reported by k0kubun (Takashi Kokubun).

13 messages 2022/07/02

[#109118] [Ruby master Bug#18893] Don't redefine memcpy(3) — "alx (Alejandro Colomar)" <noreply@...>

Issue #18893 has been reported by alx (Alejandro Colomar).

11 messages 2022/07/02

[#109152] [Ruby master Bug#18899] Inconsistent argument handling in IO#set_encoding — "javanthropus (Jeremy Bopp)" <noreply@...>

Issue #18899 has been reported by javanthropus (Jeremy Bopp).

10 messages 2022/07/06

[#109193] [Ruby master Bug#18909] ARGF.readlines reads more than current file — "JohanJosefsson (Johan Josefsson)" <noreply@...>

Issue #18909 has been reported by JohanJosefsson (Johan Josefsson).

17 messages 2022/07/13

[#109196] [Ruby master Bug#18911] Process._fork hook point is not called when Process.daemon is used — "ivoanjo (Ivo Anjo)" <noreply@...>

Issue #18911 has been reported by ivoanjo (Ivo Anjo).

9 messages 2022/07/13

[#109201] [Ruby master Bug#18912] Build failure with macOS 13 (Ventura) Beta — "hsbt (Hiroshi SHIBATA)" <noreply@...>

Issue #18912 has been reported by hsbt (Hiroshi SHIBATA).

20 messages 2022/07/14

[#109206] [Ruby master Bug#18914] Segmentation fault during Ruby test suite execution — "jprokop (Jarek Prokop)" <noreply@...>

Issue #18914 has been reported by jprokop (Jarek Prokop).

8 messages 2022/07/14

[#109207] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedYet — Quintasan <noreply@...>

Issue #18915 has been reported by Quintasan (Michał Zając).

18 messages 2022/07/14

[#109260] [Ruby master Feature#18930] Officially deprecate class variables — "Eregon (Benoit Daloze)" <noreply@...>

Issue #18930 has been reported by Eregon (Benoit Daloze).

21 messages 2022/07/20

[#109314] [Ruby master Bug#18938] Backport cf7d07570f50ef9c16007019afcff11ba6500d70 — "byroot (Jean Boussier)" <noreply@...>

Issue #18938 has been reported by byroot (Jean Boussier).

8 messages 2022/07/25

[#109371] [Ruby master Feature#18949] Deprecate and remove replicate and dummy encodings — "Eregon (Benoit Daloze)" <noreply@...>

Issue #18949 has been reported by Eregon (Benoit Daloze).

35 messages 2022/07/29

[ruby-core:109211] [Ruby master Bug#18883] parse.y: trailing comma cannot coexist with star

From: "jeremyevans0 (Jeremy Evans)" <noreply@...>
Date: 2022-07-14 20:00:07 UTC
List: ruby-core #109211
Issue #18883 has been updated by jeremyevans0 (Jeremy Evans).


zverok (Victor Shepelev) wrote in #note-1:
> As far as I understand, trailing comma is an equivalent of `*_` (unpack the rest and drop it):
> ```ruby
> x, = [1, 2, 3]
> # is the same as
> x, *_ = [1, 2, 3]
> # put 1 in x, ignore the rest, it is the shortest way to do it
> ```

Close.  `*_` will set a local variable, and allocate an extra array. `x, = [1, 2, 3]` is actually the same as `x, * = [1, 2, 3]` (same VM instructions).  However, this doesn't fully explain the issue, because `x = ` (single assignment) and `x, =` (multiple assignment) are significantly different.  It would be better to compare with:

```
x, a = [1, 2, 3]
x, a, = [1, 2, 3]
x, a, * = [1, 2, 3]
```

All of these result in the same VM instructions, indicating that a trailing comma shouldn't make a difference.

That being said, I don't think this is a bug, but I wouldn't be opposed to modifying the parser to support this as a feature, assuming it is doable.

----------------------------------------
Bug #18883: parse.y: trailing comma cannot coexist with star
https://bugs.ruby-lang.org/issues/18883#change-98346

* Author: qnighy (Masaki Hara)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
The following code is a syntax error:

```ruby
*x, y, = 1, 2 # syntax error, unexpected '='
```

although the following:

```ruby
x, y = 1, 2  # OK
x, y, = 1, 2 # OK
*x, y = 1, 2 # OK
# *x, y, = 1, 2
```

In my understanding, the trailing comma does nothing unless the lhs becomes otherwise a single assignment.

Therefore it is natural to allow the trailing comma whether `*` exists or not.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread