Better support for named argument calling

[domenic]

I'm starting to use the pattern in whatwg/infra#325 and it's not working that great.

I have to use

<a for=ReadableStream/create><var ignore>highWaterMark</var></a>

but I'd like to use something like

[=ReadableStream/create/|highWaterMark|=]

Any ideas?

[domenic]

It's also important that these <var>s not get highlighted by the var-highlighting JS when clicked.

[tabatkins]

Yeah that looks real bad.

How would you feel about <arg>ReadableStream/create/highWaterMark</arg>?

[domenic]

Works for me. I kinda like my markup shorthands instead of HTML tags, but I don't insist by any means, and I assume you're running out of character combinations :).

[tabatkins]

Yeah, I'm trying to limit grawlix in general; there's still plenty of space in the [$..$] style of tags, but short tagnames are nice too ^_^

[jyasskin]

Since a call is likely to have several arguments scoped to the same algorithm, I think we'll want to be able to default the ReadableStream/create part. As mentioned in whatwg/infra#320 (comment),

<call>[=ReadableStream/create=] with a <arg>highWaterMark</arg> of |value|</call>

might be a good syntax, where the algorithm name provides the default for= value for <arg>s. If <call> isn't in the cards for a while, we'll want to have something like

<span arg-for="ReadableStream/create">[=ReadableStream/create=] with a <arg>highWaterMark</arg> of |value|</span>

[tabatkins]

Yup, definitely my thought too.