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

Handling of Number types can be unexpected #557

Open
Jolanrensen opened this issue Jan 12, 2024 · 0 comments
Open

Handling of Number types can be unexpected #557

Jolanrensen opened this issue Jan 12, 2024 · 0 comments
Labels
research This requires a deeper dive to gather a better understanding
Milestone

Comments

@Jolanrensen
Copy link
Collaborator

Jolanrensen commented Jan 12, 2024

Currently, numbers are inferred similar to type inference in Kotlin.

For instance:

DataFrame.readJsonStr("""[ { "a": 1 }, { "a": 1.0 } ]""")

results in a column: a: Number. This can cause issues with statistics like std, as they don't support Numbers as of now: #558
It might be easier to work with if numbers would converge in the closest common ancestor in terms of information. For instance: Int + Double + Float => Float, since Floats can store all information a Double and Int holds.

This would need to be carefully considered, however, as it's inconsistent with Kotlin's type inference.

@Jolanrensen Jolanrensen added invalid This issue/PR doesn't seem right research This requires a deeper dive to gather a better understanding labels Jan 12, 2024
@Jolanrensen Jolanrensen added this to the Backlog milestone Jan 12, 2024
@zaleslaw zaleslaw removed the invalid This issue/PR doesn't seem right label Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research This requires a deeper dive to gather a better understanding
Projects
None yet
Development

No branches or pull requests

2 participants