Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: parse_type_desc maybe has some question #411

Closed
TCeason opened this issue Apr 25, 2024 · 1 comment · Fixed by #412
Closed

bug: parse_type_desc maybe has some question #411

TCeason opened this issue Apr 25, 2024 · 1 comment · Fixed by #412
Assignees

Comments

@TCeason
Copy link
Collaborator

TCeason commented Apr 25, 2024

I do an ut test_parse_type_desc on my local: if input is : Nullable(Tuple(String NULL, Array(Tuple(Array(Int32 NULL) NULL, Array(String NULL) NULL) NULL) NULL))

the output of parse_type_desc is :

  left: `TypeDesc { name: "Nullable", args: [TypeDesc { name: "Tuple", args: [TypeDesc { name: "NULL", args: [TypeDesc { name: "String", args: [] }] }, TypeDesc { name: "NULL", args: [TypeDesc { name: "NULL", args: [TypeDesc { name: "NULL", args: [TypeDesc { name: "NULL", args: [TypeDesc { name: "Int32", args: [] }] }] }, TypeDesc { name: "NULL", args: [TypeDesc { name: "NULL", args: [TypeDesc { name: "String", args: [] }] }] }] }] }] }] }`,

We can see that the Array type is dropped.

@TCeason
Copy link
Collaborator Author

TCeason commented Apr 25, 2024

cc @everpcpc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants