New Bug Encountered (?): EnumList and Lookup function

I found that a lookup function returning an EnumList, it will pass the type check, but will not be treated like a list, i.e.:
LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Towns” ) with [Towns] of type EnumList (of base type Name in my case) will be accepted when an EnumList is expected, but I cannot e.g. just add it to another EnumList of the same base type.
So e.g. this will not work:
LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Towns” ) +
LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Cities” ) ,
or LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Towns” ) + [another EnumList of same base type]

The only option I found so far to do this is by using intermediate columns:
[Col A] = LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Towns” )
[Col B] = LOOKUP ( MINROW ( “T1” , “TimeStamp” ) , “T1” , “TimeStamp” , “Cities” )
[Col C] = [Col A] + [Col B]

Is this really the intended behavior ? Thx.

The error message I am receiving is “type unknown”

This has always been my experience, and I believe the intended behavior.

Wrap LOOKUP() in SPLIT(..., ","):

SPLIT(LOOKUP(MINROW(“T1”, “TimeStamp”), “T1”, “TimeStamp”, “Towns”), ",")
+ SPLIT(LOOKUP(MINROW(“T1”, “TimeStamp”), “T1”, “TimeStamp”, “Cities”), ",")

This creates other problems, though.