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

Fixes to allow building in -std=c++20 mode. #33

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pkasting
Copy link

@pkasting pkasting commented May 4, 2022

  • Various kinds of math involving enums are deprecated, so replace with
    constexprs where necessary.
  • Types on both sides of "==" must match.

Bug: chromium:1284275

* Various kinds of math involving enums are deprecated, so replace with
  constexprs where necessary.
* Types on both sides of "==" must match.

Bug: chromium:1284275
Copy link
Owner

@aawc aawc left a comment

Choose a reason for hiding this comment

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

The changes themselves look good to me, but this repository may not be the best place to make these changes.
This repository is meant to be just a place to keep different versions of the unrar library hosted so that Chromium can pull it. The true source is: https://www.rarlab.com/rar_add.htm

I can reach out to the real maintainer of unrar to see if they are can merge these changes in their version that Chromium can then use. Would that be OK?

@pkasting
Copy link
Author

Yes, that would be great! Thanks very much.

@pkasting
Copy link
Author

Any word from upstream?

@fred-wang
Copy link

@aawc I'm also interested to know update from maintainer in order to merge #35

@pkasting
Copy link
Author

pkasting commented Jul 2, 2024

It looks like the current trunk has taken some of the fixes here (BLAKE_ALIGNMENT and BLAKE_DATA_SIZE are now constexprs and HashValue::operator==() is now const) but not others (the BLAKE2S_ constants are still enums and HashValue::operator!=() still exists, although since it's now marked const it will no longer cause any compilation problems).

Did upstream miss the remaining bits, reject them, ...? Wondering what to do with this PR.

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