Skip to content
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

Removing ambiguous definitions for is_future_range and future_range_traits #2043

Merged
merged 5 commits into from Mar 24, 2016

Conversation

hkaiser
Copy link
Member

@hkaiser hkaiser commented Mar 18, 2016

This fixes #2032. Thanks @ddemidov!

This should be merged after #2041 only

@hkaiser hkaiser added this to the 0.9.12 milestone Mar 18, 2016
@hkaiser hkaiser merged commit 9dd0810 into master Mar 24, 2016
@hkaiser hkaiser deleted the fixing_2032 branch March 24, 2016 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ambiguous template instantiation for is_future_range and future_range_traits.
1 participant