Wording change: Add types to all internal algorithm members

[inexorabletash]

Note that this isn't TypeScript or C++ - we are free to make the type annotations more specific, easier to read, etc. So there may be cases where we don't simply give an Infra or Web IDL type or rigorously follow the Infra style. Comments and suggestions welcome!

---

Preview | Diff

[inexorabletash]

One potential point of discussion - instead of just "string" e.g. in "To create argMin/argMax operation given string op, ..." we could more specifically say "operator name". And we could go further and give a definition for that term ("A operator name is a string, used internally to distinguish similar operators..."), but that's overkill IMHO.

[huningxin]

And we could go further and give a definition for that term ("A operator name is a string, used internally to distinguish similar operators...")

Or we can define an enum having all valid operator names? Maybe also overkill.

[huningxin]

LGTM, thanks much!

[anssiko]

👍

[inexorabletash]

And just to be pedantic: I now have Triage permissions (thanks!) but not Write permissions, so I still need an editor (etc) to hit the Merge button even if a PR has multiple approvals. Thanks in advance @wchao1115 😄

[anssiko]

I will merge this last open "wording change" ready-to-merge PR to let @wchao1115 focus his attention on PRs that propose normative changes.

I will ask @inexorabletash to give an overview of the recent wording change PRs on our upcoming meeting to ensure the entire WG is informed of changes that go in.