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

Should FieldPointer take instance's class instead of field class #8

Open
kotovdv opened this issue Jun 23, 2017 · 0 comments
Open

Should FieldPointer take instance's class instead of field class #8

kotovdv opened this issue Jun 23, 2017 · 0 comments
Assignees
Labels

Comments

@kotovdv
Copy link
Owner

kotovdv commented Jun 23, 2017

Should FieldPointer take instance's class instead of field class when field is not null?

Considering an example:

class MyClass{
private final Number value;
...constructor
}

Might work incorrectly in couple of comparison operations, since Number class itself does not implement Comparable interface, meanwhile his subclasses do.

Need additional investigation

@kotovdv kotovdv self-assigned this Jun 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant