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

Prepare Pycryptopp for Crypto++ changes for byte #43

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

Prepare Pycryptopp for Crypto++ changes for byte #43

wants to merge 1 commit into from

Conversation

noloader
Copy link

@noloader noloader commented Jul 17, 2017

The Crypto++ library is getting ready to change the scope of its definition for a byte. The short of it is, Crypto++ byte and C++17 std::byte can cause compile failures due to ambiguous resolutions; and the behavior of Crypto++ byte and std::byte are incompatible.

More information can be found at:

Also see Issue 42, Crypto++ and upcoming change for byte definition due to C++17

The Crypto++ library is getting ready to change the scope of its definition for a byte. The short of it is, Crypto++ byte and C++17 std::byte can cause compile failures due to ambiguous resolutions; and the behavior of byte and std::byte are incompatible.

More information can be found at:

    std::byte (https://www.cryptopp.com/wiki/Std::byte) on the Crypto++ wiki

    Issue 442, Test C++17 byte change with dry runs from various projects (weidai11/cryptopp#442)
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.

1 participant