Skip to content

Add error messages - Parsers.scala:626 and Parsers.scala:1492 #1615

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
Oct 21, 2016
Merged

Add error messages - Parsers.scala:626 and Parsers.scala:1492 #1615

merged 1 commit into from
Oct 21, 2016

Conversation

sebastianharko
Copy link

Error messages for Parsers.scala:626 and Parsers.scala:1492.

Note: I may have to bump the error message ids - depending on whether the other PR gets merged before this one.

@sebastianharko
Copy link
Author

/rebuild

@felixmulder
Copy link
Contributor

So the test that is failing is: ./tests/neg/inlinevals.scala

You can try compiling it with run tests/neg/inlinevals.scala from sbt. I think the issue is that the position has changed from when it was using syntaxError. That method uses in.offset as the pos IIRC

@sebastianharko
Copy link
Author

@felixmulder thanks for the hint ! I fixed it :-)

|
|$code2
|
|""".stripMargin
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@liufengyun has been working on modifiers with positions, and I'm thinking maybe we could enhance this further to say make the following recommendation:

This happens when you accidentally specify the same modifier twice:

private private lazy val x = ...

instead of:

private lazy val x = ...

Where this would be the user's code without the duplicate modifier. What do you think @liufengyun - can this be done with the new modifier objects?


val code1 = "s\"$new Point(0,0).toString\""

val code2 = "s\"${new Point(0,0).toString}\""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for .toString in a string interpolation, it gets called automagically :)

@sebastianharko
Copy link
Author

/rebuild

@felixmulder
Copy link
Contributor

Hmm, where the CI at?

@felixmulder
Copy link
Contributor

/rebuild

@felixmulder
Copy link
Contributor

felixmulder commented Oct 21, 2016

Hey @adriaanm and @SethTisue - could you check if something's wrong with the CI? Pretty please :)

edit: thanks guyz, seems to be alive and kicking again

@felixmulder
Copy link
Contributor

/rebuild

@adriaanm
Copy link
Contributor

adriaanm commented Oct 21, 2016

Looks like you're getting the regular sbt launcher (???) and not xsbt (which I just verified is in /usr/local/bin/sbt on behemoth-2 EDIT: looks like behemoth-1 got out of synch :-().

jenkins@ip-172-31-12-38:/home/ubuntu$ which sbt
/usr/local/bin/sbt
jenkins@ip-172-31-12-38:/home/ubuntu$ sbt -ivy
Aborting: -ivy requires <path> argument

@adriaanm
Copy link
Contributor

There's also a DNS DDOS going on.

@adriaanm
Copy link
Contributor

/rebuild

@adriaanm
Copy link
Contributor

sbt-extras bug should be resolved (scala/scala-jenkins-infra#194)

@felixmulder felixmulder merged commit a6d3723 into scala:master Oct 21, 2016
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.

3 participants