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

References to implicit inherited fields require more complex analysis #14

Open
caseif opened this issue Feb 27, 2016 · 0 comments
Open
Assignees

Comments

@caseif
Copy link
Member

caseif commented Feb 27, 2016

Currently, references to implicit fields inherited from a superclass or interface are not handled properly by Nocturne. I intend to implement a solution in which such fields are made non-selectable so as to avoid a malfunction; however, in the future this should be replaced with a system wherein these references are analyzed and replaced with a reference to an explicit field from another class.

This will likely require an overhaul of the hierarchy builder, as the current system only stores an amorphous structure of various classes which relate to each other as opposed to a true hierarchy. The current system is valid for methods, which will override those of superclasses and interfaces, but fields do not share in this behavior and thus further analysis is needed to determine an appropriate replacement.

@caseif caseif self-assigned this Feb 27, 2016
@caseif caseif added this to the 1.1 milestone Feb 27, 2016
@caseif caseif modified the milestones: 1.1, 1.2 Aug 15, 2016
@caseif caseif removed this from the 1.2 milestone Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant