Core Type Specification

[benStre]

Since we are making good progress with the implementation of the core types (refactorings might still occur), we can slowly start to think about how to formally specify the DATEX core values/types and update the outdated lists in the current spec draft.

Here's the list of core types as far as I am aware of... thoughts? anything that we need to add?
@jonasstrehle @janiejestemja @TeeB3utel

Primitives

• text "xyz text"
• integer 42
• decimal 12.34
• amount 12m/s
• null null
• boolean true, false
• endpoint @example
• url https://unyt.org

Composites

• Array [1,2,"xy"]
• Struct {x: "123", y: true}
• List (1,2,3,4,"lol")
• Map (xy: 123, (100): 'number', (true): false)
• Set Set (1,2,3,4,'xy')
• Function function xy(a: integer) (...)
• Process process xy(a: integer) (...)
• Task run (...)
• Stream x << y, Stream(...)

Special types

• type (e.g. type(1|2)
• unknown
• never?

[benStre]

For Set, Map and Struct: order of entries is irrelevant for match statements, relevant for == and ===

[jonasstrehle]

see unyt-org/datex#268