Thanks Jakob! Looks like we'll have to implement our own utf8 strings
sooner than we planned, as we need a way to access the resulting value of
the stringref.
I appreciate the detailed response!
Cheers,
Alex
On Wed, Oct 2, 2024 at 5:33 AM Jakob Kummerow
wrote:
> On Wed, Oct 2, 2024 at 5:49 AM
On Wed, Oct 2, 2024 at 5:49 AM Alex Dovzhanyn
wrote:
> Hello! Following up on this because I am experiencing some unusual
> behavior when trying to actually use stringrefs after enabling them. So
> I've enabled stringref by calling
> v8::V8::SetFlagsFromString("--experimental-wasm-stringref"), wh
Hello! Following up on this because I am experiencing some unusual behavior
when trying to actually use stringrefs after enabling them. So I've enabled
stringref by calling
v8::V8::SetFlagsFromString("--experimental-wasm-stringref"), which seems to
do the trick because now I'm able to compile a
Hi Jakob,
Thanks so much for your highly detailed response! I am building from source
so I should be able to change the feature flags, but I'll try setting the
v8 flag you mentioned first since that seems to be the less intrusive
option.
Thanks for the warning about the stringref proposal! I d
Generally speaking, libwee8 supports whatever V8 supports.
That said, the state of the stringref implementation in V8 is that (like
all early-stage proposals) it's behind an off-by-default flag:
--experimental-wasm-stringref, and libwee8 doesn't have a way to enable
such flags at runtime.
If you bu
