You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Text decoder could be a lot faster. The slowness is not inherently due to the generated API, since the JSON decoder is now acceptably fast.
Idea #1: It might suffice to change the Text decoder to work against the UTF16View instead of the UTF8View. Strings are UTF-16 internally, so the iterators and accessors for that form should be faster.
Idea #2: If the above is insufficient, the Text decoder could be overhauled to use the same binary decoding approach currently used by the JSON decoder.
Note: This is not a blocking issue for 1.0
The text was updated successfully, but these errors were encountered:
The Text decoder could be a lot faster. The slowness is not inherently due to the generated API, since the JSON decoder is now acceptably fast.
Idea #1: It might suffice to change the Text decoder to work against the UTF16View instead of the UTF8View. Strings are UTF-16 internally, so the iterators and accessors for that form should be faster.
Idea #2: If the above is insufficient, the Text decoder could be overhauled to use the same binary decoding approach currently used by the JSON decoder.
Note: This is not a blocking issue for 1.0
The text was updated successfully, but these errors were encountered: