Replies: 1 comment
-
Yes, it's general-purpose. @alexander-akait will know more, but the goals are
in order. Correctness:
No lag behind:
General purpose:
Easy API:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I saw that swc-html-parser is running against the html5lib-tests testsuite.
This is very interesting to me because I find the current state of html5 parsers in Rust not satisfying. html5ever lags behind the spec and lol-html is too hard to use. I wrote html5gum which is just the tokenizer/lexer.
What were the considerations when building your own html5 parser? Was there a set of requirements not covered by other parsers? What would be required to make it a general-purpose library, except from docs?
I see that you have an implementation of tree builder which I would love to incorporate into html5gum. Skimming through the code I think html5gum tokenizer might be faster than swc (it e.g. has fastpaths for data->data transitions), but I haven't tested it.
Beta Was this translation helpful? Give feedback.
All reactions