[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
[email protected] wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
[email protected] wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85800] [Ruby trunk Feature#14385] Deprecate back-tick for Ruby 3.
From:
shevegen@...
Date:
2018-02-25 03:25:06 UTC
List:
ruby-core #85800
Issue #14385 has been updated by shevegen (Robert A. Heiler). > I see back-ticks are used improperly all the time. > For example, I would support adding warnings and suggestions to > use system() instead of being used in a void context. Dangerous > interpolation would be one use case for keeping taint, even. I am not sure if this is a good approach. What if someone really just prefers the shorter `` rather than system()? I mean, it is not a problem for me since I use `` only in context of assigning it to a variable, and then when I inspect at the variable. For example, today, I was parsing the result of exiftools for a .pdf file in ruby. It's always a trade off how chatty ruby should be with its warnings, especially when you can not or do not want to make certain suggested changes. For example, what rubocop tells me by default about my ruby code I usually do not agree with at all. :-) ---------------------------------------- Feature #14385: Deprecate back-tick for Ruby 3. https://bugs.ruby-lang.org/issues/14385#change-70650 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: ---------------------------------------- From https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20171212Japan#From-attendees Matz hopes to deprecate backtick syntax(``) for Ruby 3. We should warn about it at Ruby 2.6 (or 2.7?) We need to consider them. * warning message * warning level * ? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>