Skip to content

Behavior of "include" or "extend" as a method #637

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 11, 2018

Conversation

aycabta
Copy link
Member

@aycabta aycabta commented Jul 11, 2018

In RDoc, include or extend can receive only constant. But those sometimes receive dynamic value through complex statements. This Pull Request fixes it.

This closes #627.

In RDoc, "include" or "extend" can receive only constant. But those
sometimes receive dynamic value through complex statements. This commit
fixes it.
@aycabta aycabta force-pushed the behavior-of-include-as-a-method branch from 04198d3 to 7655e65 Compare July 11, 2018 09:18
@aycabta aycabta merged commit ea8689b into ruby:master Jul 11, 2018
@aycabta aycabta deleted the behavior-of-include-as-a-method branch July 11, 2018 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use of include with anonymous module with method breaks further parsing
1 participant