aszecsei / catlang Goto Github PK

Should build a pratt parser for expressions instead of continuing with recursive-descent.

We can optimize the memory footprint of the compiler by creating an array of literal strings. Then, each token will simply reference an element in that array (either an existing one or creating a new one as necessary) as its literal value, rather than each token owning its own literal value string. Thus, re-used identifiers (of which there are usually many) will not create duplicate strings in memory.

Decide on syntax for error handling. Leaning towards a Rust-like Result<TSuccess, TError> strategy - definitely no exception handling. Panic should be available.

When looking at a number literal, we want to parse it into a number that Go understands, so that later stages of the compiler can use them. This value should only be stored in tokens for number literals.

Currently, numbers are assumed to be integers. We should check for the inclusion of a decimal point, and if found, interpret the value as a floating point number instead.

In addition, we should decide whether floating-point literals can start with a decimal point: should ".27" be interpreted as "0.27"?

Need to implement the language server as a sub-command.

Useful crates:

• https://crates.io/crates/lsp-server
• https://crates.io/crates/lsp-types

Enums should be able to be backed by any numeric type:

enum Alignment: U32 {
  Left, // 0
  Right = 12, // 12
  Center, // 13
}

Currently, enums are not able to be backed by a value or have their members be assigned a value.

Generic type parameters should be applicable to structs and functions. Should also finalize syntax for declaring generic type constraints.

• https://crates.io/crates/clang

Need to decide on syntax for interfaces.

volatile and const should both be able to modify types.

https://doc.rust-lang.org/rustc/codegen-options/index.html#linker-flavor