`@set` in the data does not override `@list` in the context

I ran into this issue while trying to find an acceptable output for the code in #547. It would, IMO, look like this:

{
  "@context": {
    "prop": {
      "@id": "http://schema.org/prop",
      "@container": "@list"
    }
  },
  "prop": {"@set": [
    ["foo", "bar"],
    ["baz", "qux"]
  ]}
}

I would expect the @set on line 8 to override the @container: @list in the context, so that this expands back to the original code in #547. But instead, this expands into a @list of @lists in the JSON-LD playground, PyLD, and the Ruby distiller. The @set keyword is simply ignored.

Do others share my expectation that @set in this example should override the @list from the context?

Start with the JSON-LD example and the linked #547 issue, then compare the observed expansion in the JSON-LD playground, PyLD, and the Ruby distiller. Determine whether @set should override @container @list and document the agreed behavior; no repository file or test is named in the issue.