Name already in use

It's wrong to assert that return types are always easy to infer from algorithm steps and call sites. We also shouldn't make people read through the call sites (which might be in other documents) to figure out what an algorithm returns.

For the Encoding Standard.

Part of the wording is adopted from the HTML Standard.

Follow-up: #523.

Co-authored-by: Domenic Denicola <[email protected]>

"Let (variableOne, variableTwo) be the result of functionReturningTuple." is now a valid statement.

Fixes #508.

And align the rest of the document as well.

See https://github.com/whatwg/spec-factory for details.

Fixes #388.

As suggested in passing in #446.

Closes #414.

Fixes #406.

Overall this syntax was somewhat confusing as the slash is used for many other purposes.

Fetch was using this syntax, but that is being addressed in whatwg/fetch#1339.

Fixes #127.

See whatwg/html#7251 for context.

Also fix some fallout from switching to positions rather than indices.

Previously, the spec attempted to use code unit/point indices in the substring definitions. However, this mismatched how most programming languages do substring operations, and was buggy, as noted in #402.

This changes the definitions to operate on "positions" between code units/points, instead of indices, with a note explaining the difference. The resulting prose then matches most programming languages, as well as the JavaScript specification's less-formal "substring" definition.

Closes #402.

Followup to cd60f9e.

Closes #152.

Also add "keys" and "values" as linking aliases for "get the keys"/"get the values" on maps.

Fixes #341.

See https://github.com/whatwg/spec-factory for details.

Missing a character in this example.

Helps with whatwg/meta#174.

Closes #349.

Closes #320.

* Adds "Parse a JSON string into a JavaScript value" as a thin wrapper
  around %JSON.parse%.

* Adds "serialize a JavaScript value to a JSON string", allowing
  standards to avoid the unexpected behavior of %JSON.stringify% when
  used on non-JSON-serializable JavaScript objects.

* Renames "parse JSON from bytes" to "parse JSON bytes to a JavaScript
  value", and "serialize JSON to bytes" to "serialize a JavaScript value
  to JSON bytes". (lt="" values for the old names are kept, so as not
  to break links.)

* Renames "parse JSON into Infra values" to "parse a JSON string to an
  Infra value" (again keeping the old lt="" value).

* Adds "parse JSON bytes to an Infra value".

* Minor tweaks to source syntax to uniformize on [$$] and ||.

* Minor tweaks to variable names to uniformize on "string", "bytes",
  "jsValue", and "value".

* Ensures that all exported terms in this section also have their gerund
  forms exported.

Closes #336.