RE: [Bug 25986] Signify JSON as a return value

Most return values are just documentation anyway, from a normative specification perspective. (Promise<T> is the only one I can think of that has an impact.) Adding a way to document that the object is "JSON compatible" seems just as useful as any other return value.
Sent: 2014-06-05 22:08
Subject: [Bug 25986] Signify JSON as a return value

--- Comment #2 from Anne <> ---
I don't think so. I thought it would be nice to indicate that something returns
either JSON, a Blob, or a string. `(Blob or JSON or DOMString)` seems more
clear than `any`.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 6 June 2014 06:38:11 UTC