-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Drop DottyPredef.assertFail. #10303
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
Drop DottyPredef.assertFail. #10303
Conversation
Although it is a useful thing to have, there is nothing specific to Scala 3 about it. Therefore, it does not carry its weight in `DottyPredef`.
There was a problem hiding this 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:
- Separate subject from body with a blank line
- When fixing an issue, start your commit message with
Fix #<ISSUE-NBR>:
- Limit the subject line to 72 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line ("Add" instead of "Added")
- Wrap the body at 80 characters
- Use the body to explain what and why vs. how
adapted from https://chris.beams.io/posts/git-commit
Have an awesome day! ☀️
We could save some bytes and compilation time by moving assertFail to |
I don't know if we should. But if yes, I pushed a second commit that does that. |
Something seems to be wrong with the last change |
967a6d7
to
e0728b3
Compare
Fixed now. |
Although it is a useful thing to have, there is nothing specific to Scala 3 about it. Therefore, it does not carry its weight in
DottyPredef
.