Re: [fetch] Should `body` parameter in the Response constructor nullable? (#178)

> it seems that it returning undefined might make folks suspect the property does not exist. Is that your reasoning why we should stick to null there and therefore allow it as part of the constructor too

Yeah, pretty much. There's also some vague distinction in my head between `null` as "explicitly no object" and `undefined` as "this property isn't even initialized/doesn't even exist/is left as its default" or something like that.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/178#issuecomment-164509413