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

Deprecation warning for memset and memcpy with bytestring >= 0.11.5 #220

Closed
andreasabel opened this issue Jul 12, 2023 · 1 comment · Fixed by #221
Closed

Deprecation warning for memset and memcpy with bytestring >= 0.11.5 #220

andreasabel opened this issue Jul 12, 2023 · 1 comment · Fixed by #221

Comments

@andreasabel
Copy link
Member

andreasabel commented Jul 12, 2023

$ cabal build --constraint='bytestring >=0.12' --allow-newer=bytestring
...
internal/Data/Attoparsec/ByteString/FastSet.hs:97:18: warning: [-Wdeprecations]
    In the use of ‘memset’
    (imported from Data.ByteString.Internal, but defined in bytestring-0.11.5.0:Data.ByteString.Internal.Type):
    Deprecated: "Use Foreign.Marshal.Utils.fillBytes instead"
   |
97 |             _ <- I.memset t 0 32
   |                  ^^^^^^^^
...
internal/Data/Attoparsec/ByteString/Buffer.hs:121:11: warning: [GHC-68441] [-Wdeprecations]
    In the use of ‘memcpy’
    (imported from Data.ByteString.Internal, but defined in Data.ByteString.Internal.Type):
    Deprecated: "Use Foreign.Marshal.Utils.copyBytes instead"
    |
121 |           memcpy (ptr0 `plusPtr` (off0+len0))
    |           ^^^^^^
...
@andreasabel andreasabel changed the title Deprecation warning for memcpy with bytestring-0.12 Deprecation warning for memset and memcpy with bytestring >= 0.11.5 Jul 13, 2023
@topikettunen
Copy link
Contributor

Stumbled upon accidentally the same warnings, opened a quick fix at #221

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 a pull request may close this issue.

2 participants