ara.t.howard

i'd love a pull request!

essentially, the reader must be read consistent. specifically, the first invocation needs to memo-ize the default proc, vs simply looking at the list of options. eg. ```ruby ivar = "@#{...

i'll see if i can gin up a PR

not necessarily. one would simple need to hit all readers to initialize the values *before* freezing. freezing is nice but it also means that objects are expensive, as memoization is...

@pmq20 i have hit the same issue i think ( https://github.com/pmq20/ruby-packer/issues/143 ) and looked at the build strategy for traveling-ruby which, i'm sure, you are aware of. it sure would...

@SwagDevOps the issue with rubyc attm is that it compiles on too new of a build box, acquiring symbols that are non-portable. it isn't about the OS, it's about getting...

possible solution: https://github.com/wg/wrk/issues/379

also, fwiw, i get this same issue from the reference compiled ruby here when i run it, it looks like: https://github.com/enclose-io/ruby/releases/download/v2.7.1-linux/ruby ```bash ahoward@penguin:~/tmp$ curl -sLO https://github.com/enclose-io/ruby/releases/download/v2.7.1-linux/ruby ahoward@penguin:~/tmp$ chmod 755 ./ruby...

just also noticing that the code absolute string bashes user input already: ``` ruby def sanitize_command! command.to_s.strip! if command.to_s.match("\n") @command = String.new.tap do |cs| command.to_s.lines.each do |line| cs

there aren't sane use cases for _either_ strings or arrays as *args as command arguments if you ask me - both are arbitrary. however, the code has a bunch of...