"Return the new EventSource object, but continue..."

[KiChjang]

https://html.spec.whatwg.org/multipage/comms.html#the-eventsource-interface

Return the new EventSource object, but continue these steps in parallel.

Fetch request.

I don't think there are any programming languages out there that can still execute sequential code after a return statement. Perhaps these two steps should be swapped around, and the "Fetch request" step can be instead rephrased as "Fetch request in parallel".

[domenic]

I too have always found this confusing. However, it is fairly prevalent throughout spec-ese. I'd support a pull request auditing and eliminating such occurrences, but maybe other editors would prefer to keep consistency with the existing spec ecosystem.

[annevk]

I think it's fine to move to a place where we get rid of this pattern in favor of running substeps in parallel. Whenever I write a new algorithm I already do so. (I believe a bunch of the module work adopted this old pattern though.)

[KiChjang]

@annevk If I understood correctly, that means you're eliminating the notion of "running substeps in parallel". How does the description of the replaced steps look like?

[annevk]

@KiChjang that is not correct. See https://storage.spec.whatwg.org/#dom-storagemanager-requestpersistent for an example of what I mean.

[KiChjang]

So in this case, it would look something like this:

1. Run the following substep in parallel:
   1. Fetch request.
2. Return the new EventSource object.

[annevk]

Yeah, something like that.