Error Codes

First, let’s learn to understand error messages. They’re comprised of three parts:

The first letter (message type):

E = Error
W = Warning

The second letter (error compiler location):

L = Lexer Stage
P = Parser Stage
S = Semantic Analysis
T = Symbol Table
N = Linking Stage
C = Command Line

The third part, the error number. This denotes the actual message inside of the message type and compiler location. Occasionally in alpha or debug builds an error number might show up as xxxx, this means that it hasn’t been assigned an official number yet.

[EL0000]
 ^^^
 |||
 ||+-- Message Number
 |+--- Compiler Location
 +---- Message Type

Warning

The current error code list is incomplete, a more comprehensive list will be made when the compiler is closer to a stable release.

EL0000

Message:
Unexpected End-of-File Immediately After Comment Opening

Meaning:
The compiler expected a message after the opening of a comment but the file ended instead.

EL0001

Message:
Unexpected End-of-File While Lexing Comment

Meaning:
The lexer expected a comment to extend to a newline character but the file ended instead

EL0002

Message:
Unexpected End-of-File Immediately After Comment Opening

Meaning:
The compiler ran into the end of the file while parsing a block comment

EL0003

Message:
Unexpected End-of-File In Closing of Multi-Line Comment

Meaning:
The compiler was in the process of closing a block comment when it ran into the end of the file

EL0004 [DUPLICATE] [FLAG]

EL0005

Message:
Unexpected End-of-File Immediately After Identifier Opening

Meaning:
The compiler started processing an identifier and ran into the end of the file unexpectedly

EL0006

Message:
Unexpected End-of-File While Lexing Identifier

Meaning:
The compiler ran into the end of the file while still in the process of lexing an identifier

EL0007

Message:
Unexpected End-of-File Immediately After Number Opening

Meaning:
The compiler ran into the end of the file while still in the process of lexing a number

EL0008

Message:
Unexpected End-of-File While Lexing Number

Meaning:
The compiler ran into the end of the file while still in the process of lexing a number

EL0009

Message:
Unexpected End-of-File Immediately After String Opening

Meaning:
The compiler ran into the end of the file while still in the process of lexing a string

EL0010

Message:
Unexpected End-of-File While Lexing String

Meaning:
The compiler ran into the end of the file while still in the process of lexing a string

EP0000

Message:
Expected <token> but got <token>

Meaning:
The parser was expecting a specific token, but a different one was in the spot

EP0001

Message:
Expected identifier, found <token>

Meaning:
The parser was expecting an identifier but found a different token in the spot

EP0002 [DUPLICATE] [FLAG]

EP0003 [FLAG]

Message:
Unexpected end-of-file while parsing block

Meaning:
The compiler ran into the end of the file while parsing a block of statements

EP0004

Message:
Function <name> parameter <param name> must be a valid type, currently <invalid type name>

Meaning:
One of a functions parameters isn’t a valid type

EP0005

Message:
Function <name> must derive valid type, currently <invalid type name>

Meaning:
The provided function doesn’t have a valid return type

EP0006

Message:
Invalid statement used to initialize for loop

Meaning:
The provided for loop initialization statement is not valid

EP0007 [FLAG]

Message:
Invalid statement used in for loop

Meaning:
A provided statement in the body of a for loop is invalid

EP0008

Message:
Namespace Declaration without a Name

Meaning:
A namespace was declared without a valid name afterwards

EP0009

Message:
Expected identifier or string after using but got <token>

Meaning:
An invalid token sequence was provided after the using keyword

EP0010

Message:
Unexpected Token in Expression, Found <token>

Meaning:
When parsing an expression the parser ran into a token that isn’t supported in expressions

EP0011

Message:
Expected Literal in Expression, Found <token>

Meaning:
When parsing an expression the parser expected a literal but found a different token in the spot

ES0000

Message:
Expected variable <name> to be <type> but it’s <type>, maybe cast?

Meaning:
When using a variable in a specific type context, the variable had an incompatible type

ES0001

Message:
Reference to undefined variable <name>

Meaning:
An undefined variable was used somewhere in an expression

ES0002

Message:
Invalid Binary Operation Types, Cannot use <type> With <type>, Consider Casting

Meaning:
Two types used in a binary operation are not compatible with each other

ES0003

Message:
Inline Function Call with Type Hint Doesn’t Match Function Return Type (Hint: <type>, Returns <type>)

Meaning:
A function call used a type hint but the type hint doesn’t match a possible return type of the function

ES0004

Message:
Unexpected Number of Parameters to Function <name>, Expected <value> but got <value>

Meaning:
The number of parameters passed in a function call and the number of parameters in the function definition are different

Example:

// Function Definition (3 Parameters)
fn testing(int a, int b, int c) -> void;

// Function Call (2 Parameters)
testing(10, 20);

ES0005

Message:
Type mismatch passed to function <name> in arg slot <value>, expected <type> but got <type>

Meaning:
One of the parameters passed to a function doesn’t match the expected type based on the function definition

Example:

// Function Definition (bool, int)
fn testing(bool a, int b) -> void;

// Function Call (float, int)
testing(10.0, 10);

ES0006 [FLAG]

Message:
Different types passed to forward declared function <name> in arg slot <value>, previously used <type> but <type> was passed, verify this is correct

Meaning:
Two different calls to the same forward declared function have different types in the same parameter position

ES0007 [FLAG]

Message:
Empty array literal, verify this is correct

Meaning:
There is an empty array literal.

ES0008

Message:
Array literal initialized with type <type> was passed a <type>

Meaning:
An array created with one type contains an element of an incompatible type

ES0009

Message:
Missing type hint for array literal declaration

Meaning:
A required type hint for array literal declarations is missing

ES0010

Message:
Invalid array index type, must be in the integer family, got <type>

Meaning:
Attempted to use a non-integer type to index into an array, this obviously will not work

ES0011

Message:
Expected <literal> to be Parsed as an Integer

Meaning:
The compiler expected a literal to be parsed as an integer but it was not

ES0012

Message:
Expected <literal> to be Parsed as a Float

Meaning:
The compiler expected a literal to be parsed as a float but it was not

ES0013

Message:
Cannot use <type> in the context of <type< (attempted literal upcast)

Meaning:
The type of a literal cannot be used in the context of a different incompatible type

ES0014

Message:
Cannot use <type> in the context of <type> (attempted type conversion)

Meaning:
A type cannot be used in the context of a different incompatible type

ES0015

Message:
Cannot implicitly convert <type> to <type> (would lose fractional data)

Meaning:
The compiler has detected that it needs to change types in order to work in an expression but will not implicitly convert it due to data loss, a cast is required in this situation

ES0016

Message:
Cannot implicity convert <type> to <type>

Meaning:
The compiler has detected that it needs to change types in order to work in an expression but will not implicitly convert it for some reason

ES0017

Message:
Type mismatch in variable declaration <name>, expected <type> but got <type>

Meaning:
A variable was defined with a specific type but the assignment expression resulted in a different type

ES0018

Message:
Type mismatch in variable reassignment <name>, expected <type> but got <type>

Meaning:
A variable was defined with a specific type but the re-assignment expression resulted in a different type

ES0019

Message:
Attempted to reassign variable that does not exist <name>

Meaning:
Really?

ES0020

Message:
Type mismatch in function return, expected <type> but got <type>

Meaning:
The return type of a function was expecting a specific type but got a different incompatible type

ES0021

Message:
Type mismatch in function return, expected <type> but got none

Meaning:
The return type of a function was expected to be a specific type but wasn’t anything

ES0022

Message:
Condition in if statement must be of type Boolean, got <type>

Meaning:
The conditional expression inside of an if statement was expecting to result in a boolean type but instead resulted in a different incompatible type

ES0023

Message:
Condition in while statement must be of type Boolean, got <type>

Meaning:
The conditional expression inside of a while statement was expecting to result in a boolean type but instead resulted in a different incompatible type

ES0024

Message:
Condition in for statement must be of type Boolean, got <type>

Meaning:
The conditional expression inside of a for statement was expected to result in a boolean type but instead resulted in a different incompatible type