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
UTF-8 support is not always needed. Often times, ASCII is all you need. Being able to parameterize the parser at compile time with the desired encoding would improve performance and potentially eliminate pulling in the Unicode tables. This could be highly desirable for future compile-time parsing scenarios in C++23 and beyond.
Investigate turning the lug::parser class into a lug::basic_parser template that takes the character encoding class as a template. At least support for ASCII and UTF-8 character encodings should be supported. A type alias of lug::parser can then be introduced to maintain the existing behavior with full Unicode support.
This feature might also make it easier to perform byte level parsing of binary file formats.
The text was updated successfully, but these errors were encountered:
UTF-8 support is not always needed. Often times, ASCII is all you need. Being able to parameterize the parser at compile time with the desired encoding would improve performance and potentially eliminate pulling in the Unicode tables. This could be highly desirable for future compile-time parsing scenarios in C++23 and beyond.
Investigate turning the lug::parser class into a lug::basic_parser template that takes the character encoding class as a template. At least support for ASCII and UTF-8 character encodings should be supported. A type alias of lug::parser can then be introduced to maintain the existing behavior with full Unicode support.
This feature might also make it easier to perform byte level parsing of binary file formats.
The text was updated successfully, but these errors were encountered: