You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a longstanding bug that I independently reproduced in hyperscan when building with Conan 2 which defaults to CMAKE_CXX_STANDARD 20 (c++20). The word boundary regular expression \b doesn't work correctly. A github issue has been open since 2022 regarding this: intel/hyperscan#345.
Since no fix has been merged, the workaround is to build hyperscan with a lower standard version than 20. I've test hyperscan with c++11, c++14, c++17 and this bug doesn't manifest.
Can someone pick an acceptable standard from the ones I've just mentioned and force it for the hyperscan package, to avoid this word boundary bug.
Thanks.
Package and Environment Details
Package Name/Version: hyperscan/5.4.2
Conan profile
N/A
Steps to reproduce
N/A
Logs
N/A
The text was updated successfully, but these errors were encountered:
Description
There is a longstanding bug that I independently reproduced in hyperscan when building with Conan 2 which defaults to
CMAKE_CXX_STANDARD 20
(c++20). The word boundary regular expression\b
doesn't work correctly. A github issue has been open since 2022 regarding this: intel/hyperscan#345.Since no fix has been merged, the workaround is to build hyperscan with a lower standard version than 20. I've test hyperscan with c++11, c++14, c++17 and this bug doesn't manifest.
Can someone pick an acceptable standard from the ones I've just mentioned and force it for the hyperscan package, to avoid this word boundary bug.
Thanks.
Package and Environment Details
Conan profile
N/A
Steps to reproduce
N/A
Logs
N/A
The text was updated successfully, but these errors were encountered: