Xavier Noria

My point is the following: 1. If this combination is not supported, then what happens when you set both things does not really matter on does not need to be...

The case is a bug _provided_ the feature is meant to be supported :).

@deivid-rodriguez how does Bundler know that the `activerecord` dependency expressed in `rails.gemspec` is to be found in the repo that was checked out? Does it scan recursively for .gemspecs or...

Isn't that documenting the `gemspec` method that you have available in `Gemfile`? What I have in mind is different (I think, maybe it is related behind the scenes). Let me...

Awesome, in that case, I believe this paragraph could be revised: > The gemspec method supports optional :path, :glob, :name, and :development_group options, which control where bundler looks for the...

And that is consistent with > For implicit gems (dependencies of explicit gems), any source, git, or path repository declared on the parent. This results in bundler prioritizing the ActiveSupport...

@deivid-rodriguez would love to, but EuRuKo and Rails World are eating my time. If you will, you could close to reduce open tickets. If I get a patch I can...

My thoughts: 1. In general, I believe people prefer their code to be lazy loaded by default: * This is good for fast tests workflows. * If the gem is...

I believe we cannot talk about "modes", because this is arbitrary gems. However, in CI it makes sense to eager load. You want to eager load because if CI does...

> Thing is, I suspect most gems are small enough that lazy loading doesn't make a big difference. Agree at the individual level. And if you are not concerned about...