Unicode support is easily the most expensive part of using this package, but there are many possible usages of it that do not require unicode at all, mine included. Unfortunately it is impossible to avoid the cost of your unicode implementation as there is no way to import the library that does not also import unicode, and no tree-shaking engine can remove code that is triggered by a runtime option to a used function.
This would require a breaking change to fix, but it is worth fixing.
I'm going to close this for now, as I think instead of becoming more efficient by dropping unicode parsing I'll instead just provide full unicode support (in @iter-tools/regex).
Unicode support is easily the most expensive part of using this package, but there are many possible usages of it that do not require unicode at all, mine included. Unfortunately it is impossible to avoid the cost of your unicode implementation as there is no way to import the library that does not also import unicode, and no tree-shaking engine can remove code that is triggered by a runtime option to a used function.
This would require a breaking change to fix, but it is worth fixing.