| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This matches the IDL types
|
|
Otherwise, the JS::Completion is always interpretted as an error by
ExceptionOr.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is what we call it everywhere else.
|
|
|
|
This cannot throw unless we OOM.
|
|
Only the 'start algorithm' ever returns undefined (as a null GCPtr), so
let's type the others more strictly.
|
|
|
|
|
|
|
|
|
|
This allows us to be a bit closer to the spec phrasing and matches
what we do with WritableStream
|
|
This is not documented yet, but the preferred style is getting both
upfront instead of inlining various kinds of calls in places that use
the realm and vm.
|
|
|
|
|
|
|
|
This matches what the spec does, and consolidates all of the size-
related errors in one spot instead of distributing them throughout the
various uses of enqueue_value_with_size()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will be necessary for UnderlyingSink, which is WritableStream's
equivalent of UnderlyingSource, and functions in much the same way.
|
|
|
|
|
|
|
|
|
|
|
|
This is so we can just assume it exists in Fetch APIs (while still
skipping functionality that relies on a full implementation, of
course).
|
