> You want symbols, I'm guessing for kwargs? Sure, but not necessarily just for that. It's very common to see these config hashes contain symbol keys, so no reason to not provide them as such.injekt (Lee Jarvis)
> This is not acceptable as-is though, because of the design that an `OptionParser` instance should not be modified (and may be frozen) at parsing. Yes good point. > ... I noticed that too. This functionality is not exposed though...injekt (Lee Jarvis)
Simply collecting configuration values is a very popular use for OptionParser. Code like this is quite common: ~~~ruby config = {} opts = OptionParser.new do |o| o.on "-h", "--host=HOST", "hostname" do |h| config[:host] = h ...injekt (Lee Jarvis)
Nobu you don't need the requires to reproduce. This is simply the same thing: #!/usr/bin/env ruby class Animal def bark puts 'fuck.' end end module Bark class Dog < Animal end end module Bark class Anima...injekt (Lee Jarvis)
I believe the RI output for YAML needs to be fixed to display more detailed information on usage. Currently, it displays nothing. I'm happy to start some documentation on the YAML const in lib/yaml.rb with any pointers in the right direc...injekt (Lee Jarvis)
This is perhaps not a bug, I could be missing something, but shouldn't the following code work? require 'yaml' class Person def initialize(name) @attributes = { name: name } end def method_mi...injekt (Lee Jarvis)
I like this, and I especially like the modified version from judofyr. You could also do `["abc", 3, "foo", etc].find(&Integer)` which is neat, but maybe that's a push in the wrong direction, I'm not sure.injekt (Lee Jarvis)
I believe I did compile rc1 successfully but I can't reproduce since I have updated clang, chances are it probably doesn't compile properly, though. I understand using an older version of clang would be an issue and that's fine, but w...injekt (Lee Jarvis)
clang -v returns Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn) Target: x86_64-apple-darwin12.2.0 Thread model: posix Here's the make output: https://gist.github.com/injekt/4e26a6dee2ce42fc463d Th...injekt (Lee Jarvis)
Nobuhiro, I think the point is, shouldn't we be setting SAVE_HISTORY by default? If version managers are doing this then it should tell us it should probably be done by default. Are there any reasons why this shouldn't be done?injekt (Lee Jarvis)
injekt (Lee Jarvis)12:00 PM Ruby Feature #11191: Add #to_h method to OptionParser