Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204)

Nested sequences are used in a couple of obscure ways internally but not really exposed to the general Node.js user. For instance, I'm using a nested sequence for transmitting headers to the underlying native binding in the http/2 implementation in core but the user facing API translates those into a dictionary object with a null prototype, primarily due to ease of use concerns.

For instance, when a multi-valued http/2 header is received, the structure handed off to the user looks like:

```js
{
  "header1": "value",
  "header2": ["value1", "value2"]
}
```

As opposed to:

```js
[
  ["header1": "value"],
  ["header2": "value1"],
  ["header2": "value2"]
]
```

The former is what most Node.js users would expect to be able to pass as *input*.

-- 
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/url/pull/204#issuecomment-276701850