Xavier Noria
Xavier Noria
@deivid-rodriguez indeed, it's an edge one. > In general, if Bundler is used, all dependencies should be managed by Bundler, so the require "zeitwerk" line in the script above should...
> but historically bundler never expected people to activate gems before using Bundler.setup. That's an important one, and in that sense I take this issue as a conversation about it,...
I have found a new way to hit this. 1. Gem dependency uses `path`. 2. Bundler executes the local gemspec. 3. The gemspec loads the library to set the version....
I like it. It's concise and enough.
> IMHO, Class#subclasses is not the right place to include a long explanation on how GC languages work. Agree. Also, this is not the place to explain in detail what...
> I already feel bad about wasting so much of your time/resource on discussing a small paragraph in docs No problem at all! Designing an API and writing good docs...
Followups: ```ruby c = Class.new(A) A.subclasses # => [#, D, B] ``` this, in isolation, is not guaranteed. After line 1, `c` is unusued and the GC could consider the...
> No, you'd need to exit the current method or block or whatever the scope is. One thing is how CRuby works internally today, and a different thing is which...
> You don't even know what GC.start does. _You_ being a generic _you_ there :).
Let me explain a bit more what I am saying. As a developer trying to squeeze the last drop of performance, you know the internals, you know how things work...