Expand type system #2

New issue

Open

opened 2020-04-16 17:13:51 +00:00 by zyxw59 · 2 comments

zyxw59 commented

2020-04-16 17:13:51 +00:00

(Migrated from github.com)

Currently the only types that exist are Number, Point, and Line. Once we implement if, it'd be nice to have a real boolean type instead of just using 1 and 0 as true and false.

Lists might also be useful

Currently the only types that exist are `Number`, `Point`, and `Line`. Once we implement `if`, it'd be nice to have a real boolean type instead of just using `1` and `0` as `true` and `false`. Lists might also be useful

zyxw59 commented

2025-06-29 03:59:07 +00:00

(Migrated from github.com)

we now also have String, List, Struct, and Function, although List mostly exists as an intermediate in the construction of points, or when passing arguments to functions, and there's no way to access the elements of a list.

we now also have `String`, `List`, `Struct`, and `Function`, although `List` mostly exists as an intermediate in the construction of points, or when passing arguments to functions, and there's no way to access the elements of a list.

zyxw59 commented

2025-06-29 04:02:18 +00:00

(Migrated from github.com)

Maybe it would make sense to have a Route type, and make it constructable using normal operators; this could eliminate the route statement from the parser, which is one of the more complicated ones.

Maybe it would make sense to have a `Route` type, and make it constructable using normal operators; this could eliminate the `route` statement from the parser, which is one of the more complicated ones.