Skip to content

Fix #5441: Primitive operations on Long with Float argument have different semantics from Java #9962

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 8, 2020

Conversation

prolativ
Copy link
Contributor

@prolativ prolativ commented Oct 7, 2020

No description provided.

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 ("Add" instead of "Added")
  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! ☀️

@smarter
Copy link
Member

smarter commented Oct 7, 2020

It looks like the corresponding patch in scalac is slightly different: https://github.com/scala/scala/pull/7435/files, any reason to do things differently? If not it'd be good to do the same thing they do to keep the diff between the two backent as small as possible.

@prolativ
Copy link
Contributor Author

prolativ commented Oct 7, 2020

@smarter there were a few comments to the original PR that were not taken into account because the PR got merged too early by accident so I introduced the requested changes here

@prolativ prolativ force-pushed the fix-long-and-float-max-value-type branch from d79a5ca to 6c7ac2f Compare October 7, 2020 12:41
@smarter
Copy link
Member

smarter commented Oct 7, 2020

I see, but if the code is equivalent I would prefer going with the scalac version, just so that when we diff the two we don't get confused about why there's a difference here (alternatively we could update both the dotty and scalac and backend at the same time, but it doesn't seem worth it if the code is equivalent anyway).

@prolativ prolativ force-pushed the fix-long-and-float-max-value-type branch from 6c7ac2f to 9d96d4b Compare October 7, 2020 12:46
@prolativ
Copy link
Contributor Author

prolativ commented Oct 7, 2020

OK, using the implementation from scala repo

Copy link
Member

@smarter smarter left a comment

Choose a reason for hiding this comment

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

Thanks!

@smarter smarter merged commit 1306911 into scala:master Oct 8, 2020
@Kordyjan Kordyjan added this to the 3.0.0 milestone Aug 2, 2023
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.

4 participants