[Webkit-unassigned] [Bug 172256] It should be a runtime error to call ExceptionOr::releaseReturnValue() more than once

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 18 09:36:30 PDT 2017


--- Comment #1 from Darin Adler <darin at apple.com> ---
I guess we can do this.

We do this for Ref by asserting the pointer is not null in Ref::leakRef. We don’t do this for RefPtr.

Longer term I think we want to move from ExceptionOr to std::expected. Is that right? If so, we should figure out if std::expected can assert for cases like this.

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/20170518/f3de2940/attachment.html>

More information about the webkit-unassigned mailing list