Skip to content

Move "type argument must be fully defined" message to case class scheme #2779

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

Conversation

gvolpe
Copy link
Contributor

@gvolpe gvolpe commented Jun 18, 2017

Move "type argument must be fully defined" message to new error message scheme using WilcardOnTypeArgumentNotAllowedOnNew.

…ge scheme using WilcardOnTypeArgumentNotAllowedOnNew.
Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

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

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Added" instead of "Add")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

@gvolpe gvolpe mentioned this pull request Jun 18, 2017
Copy link
Contributor

@felixmulder felixmulder left a comment

Choose a reason for hiding this comment

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

Otherwise LGTM :)

@@ -91,6 +91,7 @@
AnonymousFunctionMissingParamTypeID,
SuperCallsNotAllowedInlineID,
ModifiersNotAllowedID,
WildcardOnTypeArgumentNotAllowedOnNewID
Copy link
Contributor

Choose a reason for hiding this comment

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

This line should end in , so that the diff is single lines :)

(omg, java has trailing commas! 🔥 🔥 🔥 )

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done! :)

@felixmulder
Copy link
Contributor

Great, will merge once tests pass (=

@felixmulder felixmulder merged commit 3242e86 into scala:master Jun 19, 2017
@gvolpe gvolpe deleted the wildcard-on-type-argument-not-allowed branch June 19, 2017 11:19
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