Skip to content

[Bug] Kipper Parser does not recognise nested generic types Array<Array<T>> #736

Description

@Luna-Klatzer

Is there an existing issue for this?

  • I have searched the existing issues

I am following the documentation's guide

  • I have read the documentation

This issue exists in the latest version

  • I am using the latest version

Current Behavior

The Kipper Parser despite having been initially designed with nested types in mind seems to not correctly parse the nested array type expression Array<Array<num>> unless spaces are added for clarification, for example with the combination Array< Array<num> >.

If the spaces are present to distinguish the type then no crash is encountered during the parsing step.

Expected Behavior

Array<Array<num>> should be recognised by the Parser and correctly passed onto the semantic analysis step of the compilation.

Steps To Reproduce

  1. Use type expression Array<Array<num>>

Environment

  • Kipper: 0.12.1

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugBug or issue in the language or API

Type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions