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

A test case for a name binding progression #3515

Merged
merged 1 commit into from Feb 12, 2014

Conversation

retronym
Copy link
Member

I noticed the change when adapting Slick to work with
Scala 2.11 in AbstractSourceCodeGenerator.scala.
The behaviour changed in a70c821.

This commit locks down the new, correct behaviour with a test.

Review by @gkossakowski

/cc @szeiger, @cvogt

I noticed the change when adapting Slick to work with
Scala 2.11 in `AbstractSourceCodeGenerator.scala`.
The behaviour changed in a70c821.

This commit locks down the new, correct behaviour with a test.
@gkossakowski
Copy link
Member

LGTM.

Thanks!

gkossakowski added a commit that referenced this pull request Feb 12, 2014
A test case for a name binding progression
@gkossakowski gkossakowski merged commit 2240464 into scala:master Feb 12, 2014
@som-snytt
Copy link
Contributor

OK, I get it now.

http://stackoverflow.com/q/21736635/1296806

The only downside is that every time you run the test, you will see "ambigious" [sic] in the output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants