[#63592] [ruby-trunk - Bug #10009] IO operation is 10x slower in multi-thread environment — normalperson@...
Issue #10009 has been updated by Eric Wong.
3 messages
2014/07/08
[#63682] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/13
[#63703] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/14
[#63743] [ruby-trunk - Bug #10037] Since r46798 on Solaris, "[BUG] rb_vm_get_cref: unreachable" during make — ngotogenome@...
Issue #10037 has been updated by Naohisa Goto.
3 messages
2014/07/15
[#64136] Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb — "Jeffrey 'jf' Lim" <jfs.world@...>
As per subject.
4 messages
2014/07/31
[#64138] Re: Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb
— "Jeffrey 'jf' Lim" <jfs.world@...>
2014/07/31
On Thu, Jul 31, 2014 at 6:03 PM, Jeffrey 'jf' Lim <[email protected]>
[ruby-core:63906] [ruby-trunk - Feature #10065] Make `gem env` command output valid YAML
Issue #10065 has been updated by Eric Hodel. I don't understand the value of loading the output of `gem env` as YAML when you can query the fields directly from RubyGems itself. With the exception of subcommands of `gem env` such as `gem env path` and `gem env home` the output of gem commands is not API. I don't want to encourage parsing the output as YAML and I don't want people to clumsily jump through hoops (Hash inside a single-element Array) when real API exists. ---------------------------------------- Feature #10065: Make `gem env` command output valid YAML https://bugs.ruby-lang.org/issues/10065#change-47940 * Author: David MacMahon * Status: Feedback * Priority: Normal * Assignee: Eric Hodel * Category: lib/rubygems * Target version: ---------------------------------------- The output of `gem environment` is close to being valid YAML, but the `GEM CONFIGURATION` section uses `key => value` instead of `key: value` so the output cannot be parsed by YAML. The attached patch changes just one line to make the output of `gem environment` be valid YAML. I could not find a specification for the output of the `gem environment` command so I am filing this as a feature request rather than as a bug. The attached patch is the minimum change necessary to create valid YAML. I think the structure of the resulting YAML output is not optimal. It is currently a one element Hash whose only value is an Array of one element Hashes. Is it preferable to address that in a separate feature request or as an expansion of this one? ---Files-------------------------------- 0001-Make-gem-env-command-output-valid-YAML.patch (1.12 KB) -- https://bugs.ruby-lang.org/