| > U+093b is still in the BMP I'm sorry, I don't know what that means. If you have a specific character you'd like me to try then please tell me what it is. My Unicode expertise is quite limited. > I am not sold on lens-regex-pcre documentation Nor me. It seems to leave a lot to be desired. In fact, I don't see the point of this lens approach to regex. > "anything that works in PCRE will work" comes across as very dismissive Noted, thanks, and apologies. That was not my intention. I was trying to make a statement of fact in response to your question. > By the way, what text encodings for source files are supported by GHC? UTF-8 I think. For example, pasting that character into GHC yields: ghci> mapM_ T.putStr ("foo bar ः baz" ^.. [regex|\p{Mc}|] . match)
ः
> What string-like types are supported?ByteString (raw byte arrays) and Text (Unicode, internal representation UTF-8), as you can see from: https://hackage.haskell.org/package/lens-regex-pcre > What version of PCRE or PCRE2 does it use? Whatever your system version is. For me on Debian it's: Package: libpcre3-dev
Source: pcre3
Version: 2:8.39-15
|