[Webkit-unassigned] [Bug 234967] JSC::Wasm::setWasmTableElement() falls through ASSERT_NOT_REACHED()

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 21 09:23:32 PST 2022


Keith Miller <keith_miller at apple.com> changed:

           What    |Removed                     |Added
                 CC|                            |keith_miller at apple.com

--- Comment #2 from Keith Miller <keith_miller at apple.com> ---
I don't think it matters if it returns `true` or `false`. That return boolean is to flag whether an Out of Bounds memory exception should be thrown but any access triggering one of those asserts isn't out of bounds.

Do you think that an OoB exception is better than a no-op if we have a bug in our implementation? It seems to me a no-op is easier to work around for a dev?

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220121/98a67f60/attachment.htm>

More information about the webkit-unassigned mailing list