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. ________________________________ From: bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org> Sent: ý2014-ý06-ý05 22:08 To: public-script-coord@w3.org<mailto:public-script-coord@w3.org> Subject: [Bug 25986] Signify JSON as a return value https://www.w3.org/Bugs/Public/show_bug.cgi?id=25986 --- Comment #2 from Anne <annevk@annevk.nl> --- 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