ActiveRecord::Base.compute_type swallows NoMethodError

If you have a model that has an invalid method at the class level, like so:

class InvalidModel < ActiveRecord::Base
  not_a_real_method
end

and another model that uses it as an association:

class OtherModel < ActiveRecord::Base
  has_many :invalid_models
end

when InvalidModel is autoloaded via something like other_model_instance.invalid_models, it should raise a NoMethodError.

However, the current implementation of compute_type, which Reflection calls, swallows every NameError assuming that means a constantize failure. NoMethodError is a subclass of NameError, though, so you just get an "uninitialized constant OtherModel::InvalidModel" error. Very misleading, and it didn't work like that in Rails 2.x.

I have a patch & test forthcoming.