New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
url/url: Add URL parser #476
Conversation
Codecov ReportBase: 86.91% // Head: 80.49% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #476 +/- ##
==========================================
- Coverage 86.91% 80.49% -6.43%
==========================================
Files 84 85 +1
Lines 4066 4521 +455
==========================================
+ Hits 3534 3639 +105
- Misses 532 882 +350
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
4e62335
to
0044280
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I started write a lot of extra comments that I've deleted, but then talked with @robinlinden and he thought that it was still reasonable to add some comments, if for no other reason than to start a conversation. Perhaps I'll readd the deleted comments at some point, depending on how this first set evolves.
I have a few qualms to how the spec defines URI parsing behavior. But I'm not sure which option is better, between trying to improve/reduce the implementation, or conforming exactly to the spec as written.
f7bf389
to
cf9a2fb
Compare
5c48612
to
bfb2280
Compare
9c3959e
to
fc924cc
Compare
f33bc79
to
f055091
Compare
a49c5bf
to
3eb442a
Compare
d5a50ef
to
277e14f
Compare
You could use https://github.com/ada-url/ada instead of implementing from scratch. |
Technically yes, but we won't for a few different reasons:
I'm assuming you had reasons to implement ada-url from scratch rather than using something like Boost.url as well. :P |
Yes, definitely makes sense.
Yes, performance. Ada is 50% faster than Boost. https://www.yagiz.co/announcing-ada-url-parser-v2-0 And Boost follows RFC 3986 which is a lot different than WHATWG url spec |
aaceabc
to
9f68de6
Compare
Disabling |
I was able to reproduce the hang locally and got a call stack from clang-tidy-15:
Looks like other people are hitting the same issue: llvm/llvm-project#55530, so I guess it'll stay disabled for a while. |
WIP. Comments, questions, concerns, death threats?