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
My code is written poorly, so it can be improved and we can write a guide or list of tips for writing more performant parsers.
The library is slow and we should accept that, so we should remove the "fast" advertising and instead focus on the other features. Maybe we should even add warnings that this is not a very performant library for some use cases.
The library is slow but we should not accept that, so we should figure out why that particular benchmark is so slow and optimize the library.
Perhaps the best course of action is to do (2) first (because it is easy) and try to do (3) later.
Update: I think I see a few optimization opportunities in the dumped Core of that code:
<<|>, <|>, <$, <*, *> and <*> are not inlined
pSatisfy is not even specialized
The text was updated successfully, but these errors were encountered:
uu-parsinglib
is much slower than all other popular parsing libraries for parsing a simple arithmetic expression language.Here is the source code I wrote for this benchmark.
I think there are three options moving forward:
Perhaps the best course of action is to do (2) first (because it is easy) and try to do (3) later.
Update: I think I see a few optimization opportunities in the dumped Core of that code:
<<|>
,<|>
,<$
,<*
,*>
and<*>
are not inlinedpSatisfy
is not even specializedThe text was updated successfully, but these errors were encountered: