At the moment the digest extension uses const_missing to implement autoload. Unfortunately there's a race condition: another thread can run after the constant is defined, but before it is initialized. (http://git.io/YW3bbA) There's a ...Conrad.Irwin (Conrad Irwin)
This bug also affects pry: https://github.com/pry/pry/issues/880. Our use-case is slightly different because we are doing TOPLEVEL_BINDING.eval("some code", "/absolute/path.rb"). I think that when an absolute path is set in eval, then...Conrad.Irwin (Conrad Irwin)
At the moment the maximum size of the stack is 32. The comment implies this should be enough for arrays with up to 2**32 elements, but it's possible to create larger arrays on some big systems. I was not able to trigger a bug with: ([...Conrad.Irwin (Conrad Irwin)
If a library that you require in the -r flag of ruby evals things in TOPLEVEL_BINDING (e.g. RUBY_OPT=-rbundler/setup), then the local variables will show up in TOPLEVEL_BINDING.eval("local_variables"), but they raise a NameError if you t...Conrad.Irwin (Conrad Irwin)
Hey ko1, Your debugging API looks good :). It would be great to do this in a gem, but we can't create binding objects anymore due to changes in symbol visibility. (for 1.9 we used rb_vm_make_env_object, but it's now not exported, see [...Conrad.Irwin (Conrad Irwin)
Currently works like this: ```ruby "".split(",", -1) # => [] ``` According to the documentation, blank fields should not be stripped when a negative offset is provided. I expect: ```ruby "".split(",", -1) # => [""] ```Conrad.Irwin (Conrad Irwin)
Conrad.Irwin (Conrad Irwin)07:52 AM Ruby Bug #9494 (Closed): Race condition in autoload of Digest::SHA256, etc.