fix respond_to blowing up because of extra include_all argument

[grosser]

calling respond_to?(:xxx, true) on Arturo blows up, instead of fixing it, how about we just kill that feature :)

@jamesarosen

[jamesarosen]

Blows up how?

Removing the feature means bumping the major version, which we can do.

[grosser]

ArgumentError since it's called with 2 instead of 1
I'd rather get rid of this feature / have less magic, not sure if you like
it / want to keep it.

On Thu, Jun 26, 2014 at 3:34 PM, James Alexander Rosen <
notifications@github.com> wrote:

Blows up how?

Removing the feature means bumping the major version, which we can do.

—
Reply to this email directly or view it on GitHub
#76 (comment).

[jamesarosen]

Isn't it as easy as changing it to the following?

def respond_to?(symbol, include_private = false)
  symbol.to_s =~ ENABLED_FOR_METHOD_NAME || super
end

[grosser]

yes, but I did not like that feature, so I was thinking, why not kill it ?
:)

On Thu, Jun 26, 2014 at 3:54 PM, James Alexander Rosen <
notifications@github.com> wrote:

Isn't it as easy as changing it to the following?

def respond_to?(symbol, include_private = false)
symbol.to_s =~ ENABLED_FOR_METHOD_NAME || superend

—
Reply to this email directly or view it on GitHub
#76 (comment).

[jamesarosen]

I don't have any particular love for the feature. We should deprecate it first, though.

[grosser]

this should be ready to merge too

[grosser]

release, then merge this + release major bump ?

[jamesarosen]

I'm traveling today. I can do releases and merges tomorrow.