Intendend behaviour for setting @list in Context but using set objects as values

[WhiteGobo]

What is the intended behaviour, when using a term definition, that associates the term with a list but then use a set object as value? For example this jsonld data:

{
  "@context": {
    "nick": {
      "@id": "http://xmlns.com/foaf/0.1/nick",
      "@container": "@list"
    }
  },
  "@id": "http://example.org/people#joebob",
  "nick": {
    "@set": [
      "joe",
      "asdf"
    ]
  }
}

In the jsonld playground, it just uses the set object as list object(permalink to playground):

{
  "@id": "http://example.org/people#joebob",
  "http://xmlns.com/foaf/0.1/nick": {
    "@list": [
      "joe",
      "asdf"
    ]
  }
}

[BigBlueHat]

@WhiteGobo my guess is that @list is taking precedence because it's adding "meaning" (ordering). Notably, if you switch the @set and @list lines, the @list value will still "win". That's my theory, though...

@davidlehn any ideas? We should probably add tests for this at minimum.

[WhiteGobo]

As far as i understand, the relevant parts in the algorithm api are 13.4.11.2), 13.11) and 17) but i haven't seen anything else, where this is discussed any further. But i'm not smart enough to understand the behavior just from the algorithm api.