Ruby Issue Tracking System

02/18/2018

05:25 PM Ruby Bug #14485 (Closed): For File#path.tainted? and File#to_path.tainted? should match original.tainted?

Problem: if you create a File object using an untainted path, File#path and File#to_path return identical strings except they are tainted. That's counter-intuitive. If the input path has been properly vetted then File should not taint it... tscheingeld (Terry Scheingeld)

06/13/2017

02:22 AM Ruby Feature #13518: Indented multiline comments

nobu (Nobuyoshi Nakada) wrote:
> How about that matching indentation of `=begin` and `=end`?
> ...
Makes sense to me.
tscheingeld (Terry Scheingeld)

05/06/2017

10:13 PM Ruby Feature #13518: Indented multiline comments

duerst (Martin Dürst) wrote:
> `=begin`/`=end` are rare, and it's better to make them stick out.
I would make the case that `=begin`/`=end` is rare because it can't be indented. Multiline comments are very handy. It makes syntax high... tscheingeld (Terry Scheingeld)

04/30/2017

12:17 AM Ruby Feature #13518: Indented multiline comments

nobu (Nobuyoshi Nakada) wrote:
> Possible of course, but I'm not a big fan of this.
Respect for your ability to quickly modify the code for what I suggested.
Just to clarify: are you not a big fan of the feature request in general... tscheingeld (Terry Scheingeld)

04/28/2017

02:47 AM Ruby Feature #13518 (Rejected): Indented multiline comments

I'd like to submit the idea that multiline comments could be indented. That is, `=begin` and `=end` do not have to start at column zero. That would allow for more flexibility in documenting and commenting code. tscheingeld (Terry Scheingeld)