[#106341] [Ruby master Bug#18369] users.detect(:name, "Dorian") as shorthand for users.detect { |user| user.name == "Dorian" } — dorianmariefr <noreply@...>
Issue #18369 has been reported by dorianmariefr (Dorian Mari辿).
14 messages
2021/11/30
[#106351] [Ruby master Bug#18371] Release branches (release information in general) — "tenderlovemaking (Aaron Patterson)" <noreply@...>
Issue #18371 has been reported by tenderlovemaking (Aaron Patterson).
7 messages
2021/11/30
[ruby-core:106270] [Ruby master Bug#18363] `make clean` should consistently handle generated files otherwise it can break the build.
From:
"ioquatix (Samuel Williams)" <noreply@...>
Date:
2021-11-25 06:33:29 UTC
List:
ruby-core #106270
Issue #18363 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #18363: `make clean` should consistently handle generated files otherwise it can break the build. https://bugs.ruby-lang.org/issues/18363 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Running `make clean` will cause `ext/ripper/ripper.c` to be regenerated but not `parse.c` and this causes problems if bison is incompatible with previous version, because `ripper.c` will be regenerated with a different version of bison. nobu: Ah, yes, concatenating ripper.y and ripper.c to $cleanfiles, in ext/ripper/extconf.rb. samuel: Can this solve the problem so make clean does not remove it? nobu: I think so. `eventids*.c` also should be removed by distclean instead. -- 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>