Re: [whatwg/fetch] Allow used body replacement in Request constructor (#675)

Amended to move the disturbed or locked check closer to where it's relevant: right before the *inputBody* piping. To me, it would make most sense to either put the check in the *inputBody* piping substeps, or make it implicit in the piping itself, as I mentioned. Until that decision is finalized, this seems like the best we can do: the "critical line" between the read-only part of the constructor and the state-modifying part remains in the top-level steps (as opposed to the piping substeps, which are conditional); the piping operation is guaranteed not to throw; and the check and the piping operation are written as close to each other as possible to make future maintenance easier.

-- 
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/fetch/pull/675#issuecomment-370531967