Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691)

I agree that we shouldn't require implementations to do a double lookup for
`transformer.transform`. Retaining the ability to easily perform stream
transforms without JS involvement is important.

I also agree that your proposed change 2) is better. Yes, it'd be different
from the source and sink handling, but it'd be in a very obvious way. That
is, as soon as you tried changing the transformer's `transform` method (be
it through a straight property set or a prototype change), you'd realize
that it doesn't have an effect.

Additionally, there isn't really a loss of flexibility: you can always e.g.
have the `transform` method forward to another function that's under your
control, or check a flag on the receiver.


-- 
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/issues/691#issuecomment-285358688