Is your feature request related to a problem? Please describe.
Currently, our programming language only tracks line and column positions for tokens. However, this can be limiting, especially when dealing with multi-character tokens like keywords (e.g., fun). Right now, position tracking only picks the first letter, which can be misleading when identifying token locations. Additionally, some compiler errors are inaccurately positioned, making debugging more difficult than necessary.

Describe the solution you'd like
Introducing token spans would enhance positional accuracy in our language. Instead of relying solely on line and column numbers, spans would specify the start and end positions of tokens, ensuring precise representation. This improvement would also help refine compiler error locations, providing more accurate diagnostic messages.

Additional context
This change would improve both compiler error reporting and general token tracking, making debugging clearer and improving usability. By implementing token spans, we can provide better feedback to developers and enhance code analysis in our language.