Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)

@jyasskin commented on this pull request.



> @@ -7471,12 +7474,11 @@ value when its bit pattern is interpreted as an unsigned 64 bit integer.
 
 <div id="USVString-to-es" algorithm="convert an USVString to an ECMAScript value">
 
-    An IDL {{USVString}} value is [=converted to an ECMAScript value|converted=]
-    to an ECMAScript value by running the following algorithm:
-
-    1.  Let |scalarValues| be the sequence of [=scalar values=] the {{USVString}} represents.
-    1.  Let |string| be the sequence of [=code units=] that results from encoding |scalarValues| in UTF-16.
-    1.  Return the String value that represents the same sequence of [=code units=] as |string|.
+    The result of [=converted to an ECMAScript value|converting=]
+    an IDL {{USVString}} value to an ECMAScript
+    value is the String
+    value that represents the sequence of [=code units=]
+    in the IDL {{USVString}}.

We don't right now, so I'd like to not add that requirement to this PR.
Memory sizes on today's consumer hardware aren't actually big enough to exceed the limit (~9 petabytes), so in practice you'd crash the renderer before getting here, which we also don't encode into specifications. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/pull/1287#discussion_r1157465016
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1287/review/1371309664@github.com>