- From: Adam Rice <notifications@github.com>
- Date: Tue, 05 Dec 2017 23:24:53 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 6 December 2017 07:25:18 UTC
I would be happier if I knew why the ES version of GetMethod squashes `null` to `undefined`. I can't make sense of it. ```javascript new TransformStream({ transform: null }); ``` doesn't look like a sensible way to create an identity transform, it just looks like nonsense to me. It's not like we intend for people to write `{ transform: undefined }`, there's just no point in disallowing it. So, in the absence of a compelling justification for squashing `null` to `undefined`, I'd prefer to keep our existing semantics. I plan to proceed with option 4: inline GetMethod as it's only used in two places anyway. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/pull/860#issuecomment-349557077
Received on Wednesday, 6 December 2017 07:25:18 UTC