Unify tables/set/vectors/records

Description

Internally, tables/sets/vectors/records are all handled separately at many locations inside the interpreter (tables and sets sometimes are handled together, and sometimes aren't). I believe we should be able to unify much of that code in some form, like by moving more into a parent class CompositeType.

I'd like to see most of these if ( is-it-type-A ) … if ( is-it-type-B ) … go away.

That would also make it much easier to implement a real list type.

Environment

None

Assignee

Unassigned

Reporter

Robin Sommer

Labels

External issue ID

437

Components

Priority

Normal
Configure