GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||
GeezerVison is showing github.com — deps: replace url parser with Ada by anonrig · Pull Request #46410 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
8f4d1a4 to
4a68c84
Compare
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
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.
There was an error while loading. Please reload this page.
21adb01 to
6f070dc
Compare
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.
There was an error while loading. Please reload this page.
You're right. This pull request does not remove them. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
5e1e1ac to
a1c7401
Compare
|
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@anonrig it might very well be related to parsing the debugger websocket url |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
eb45d67 to
17d3ed7
Compare
|
I see right now Ada has Windows-specific IDNA handling using 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.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
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.
There was an error while loading. Please reload this page.
PR-URL: #46410 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
PR-URL: #46410 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
|
@nodejs/lts I've put
baking-for-lts
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #46410 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
@richardlau Should we remove the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
@nodejs/lts thoughts? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'd be ok for a backport to active v18.x, not earlier. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@anonrig this will need a backport to v18.x. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
URL API: ensure it roundtrips for opaque paths Investigate slownew URL
custom protocol parse result is different from chrome and firefox
Bug in WHATWG URL parsing
Performance of WHATWG URL API
There was an error while loading. Please reload this page.