René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why is encoding not in the type?","articleBody":"Wasm engines that know available encoding statically would sometimes be able to generate more efficient code, especially when compiling without dynamic profile information.\r\n\r\nThen we can have instruction to convert between different encodings. Conversion result can also be cached to external hash table (or to an object slot) by engine to avoid repeating the same conversion multiple types.\r\n\r\nWould JS embeddings require wrapping JS string with an extra Wasm string object in order to provide an extra WTF-8 slot? Knowing WTF-16 encoding statically would help to avoid that. \r\n\r\nThis also could scale better with adding more encodings in the future. More than two encoding slots per objects would mandate indirect access, right?","author":{"url":"https://github.com/skuzmich","@type":"Person","name":"skuzmich"},"datePublished":"2020-11-05T12:04:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/3/universal-strings/issues/3"}