Best to wait until we have full typing of built-in components (e.g. #435)
floatarray
Array of float
✔️ float[] - requires TypeExpression lookup
intarray
Array of integer
✔️ integer[] - requires TypeExpression lookup
boolarray
Array of Boolean
✔️ boolean[] - requires TypeExpression lookup
stringarray
Array of string
✔️ string[] - requires TypeExpression lookup
vector2darray
Array of vector2d
✔️ vector2d[] - requires TypeExpression lookup
colorarray
Array of color
Can be completed once color is defined
timearray
Array of time
Can be completed once time is defined
nodearray
Array of SceneGraph node object reference
Can be completed once node is defined
assocarray
Associative array
This is a special case of object - will benefit from #435
array
Array of objects - type specifier can be either array or roArray
✔️ - will benefit from #435
rect2D
An associative array with 4 float values: (x, y, width, height)x and y represent the coordinates of the top left corner of the rectangle
basically an interface!
rect2DArray
Array of rect2D associative arrays
Can be completed once rect2d is defined
Concerns:
These are really common words, (time, color, etc)... perhaps the actual keyword could be something like timeType...
Another option is to put them in a namespace: SceneGraph.time ... etc.
SceneGraph has a bunch of field types that could also be "first-class" types in Brighterscript.
From https://developer.roku.com/en-ca/docs/references/scenegraph/xml-elements/interface.md --
integer
)string
)boolean
)float[]
string
float[]
- requires TypeExpression lookupinteger[]
- requires TypeExpression lookupboolean[]
- requires TypeExpression lookupstring[]
- requires TypeExpression lookupvector2d[]
- requires TypeExpression lookupcolor
is definedtime
is definednode
is definedobject
- will benefit from #435rect2d
is definedConcerns:
These are really common words, (time, color, etc)... perhaps the actual keyword could be something like
timeType
... Another option is to put them in a namespace:SceneGraph.time
... etc.