jakobkummerow
jakobkummerow
Discussions around this proposal have shown that extending `Math` functions with BigInt support is difficult (e.g.: transcendental functions are intractable; `max`/`min` run into surprisingly difficult "how to spec this?" questions...
Don't do it.
TL;DR: I'm very skeptical of this proposal. I'll try to explain why below. In summary, I believe that the use cases are nicely served by user-space libraries, and libraries would...
The `stringview_wtf16.slice` operation creates a string S2 that's a substring of another string S1. V8 originally implemented this by reusing its existing machinery for creating string slices, i.e. S2 would...
It turns out that converting primitive values (`i32`/`i64`/`f32`/`f64`) to `stringref` is a fairly common use case in practice. Obviously, this _can_ be done using the existing instruction set (e.g. by...
Sufficiently advanced engines tend to have a specialized internal string representation for ASCII-only strings (V8 certainly does; I'm pretty sure other existing engines do too) [1]. There are also some...
Currently, the spec text for the various string creating instructions says that the result has type `stringref`, e.g.: ``` (string.new_wtf8 $memory $wtf8_policy ptr:address bytes:i32) -> str:stringref (string.concat a:stringref b:stringref) ->...