| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
There was a problem hiding this comment.
Something that I think should be experimented upon is to avoid copying all data back-and-forth every time a field is updated.
Maybe it might be better to fetch them from C++ every time they are accessed, or possibly use tricks to use the V8 fast API.
Sorry, something went wrong.
I think that has always been possible, with or without Ada? It's kept for compatibility reasons, not performance.
We probably still want to run the JS tests to make sure that the JS glues work properly |
Sorry, something went wrong.
You're right. This pull request does not remove them. |
Sorry, something went wrong.
|
@anonrig it might very well be related to parsing the debugger websocket url |
Sorry, something went wrong.
|
I see right now Ada has Windows-specific IDNA handling using IdnToAscii. I'm a little concerned about this, as it would introduce platform-dependent URL parsing results. I also doubt Windows's IdnToAscii implements UTS46 fully. I see plans to switch to an internal implementation (ada-url/ada#89) which would alleviate my concern. Do note though, that there are (still) outstanding issues with UTS46 on the spec side (see whatwg/url#744). (Context: I helped create the previous WHATWG URL parser, and also maintain https://github.com/jsdom/tr46.) |
Sorry, something went wrong.
When ICU is unavailable and we are under Windows, then ada falls back on Windows functions. That is correct. Wherever we are, if ICU is available, we rely on ICU. |
Sorry, something went wrong.
PR-URL: #46410 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com>
PR-URL: #46410 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com>
|
@nodejs/lts I've put baking-for-lts PRs that need to wait before landing in a LTS release. on this -- I feel we should err on the side of caution and allow more time for this in current releases before considering for LTS. |
Sorry, something went wrong.
PR-URL: #46410 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com>
@richardlau Should we remove the backing-for-lts label? In total, there were 2 issues reported and all of them is fixed in 19.8.0. |
Sorry, something went wrong.
@nodejs/lts thoughts? |
Sorry, something went wrong.
|
I'd be ok for a backport to active v18.x, not earlier. |
Sorry, something went wrong.
|
@anonrig this will need a backport to v18.x. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This work was done in collaboration with me, @miguelteixeiraa and @lemire. I would also like to thank @addaleax and @ronag for their help.
This pull request replaces the existing URL parser with Ada, a fast spec-compliant URL parser written from scratch using modern C++ focused on performance.
A little bit about Ada:
The possibilities with this pull request:
Side Note: Current benchmarks show up to 87% faster URL parsing, with similar but sometimes faster execution speeds compared to url.parse.
Fixes #46332
Fixes #46063
Fixes #30334
Fixes #44476
Fixes nodejs/performance#33
Closes #41220