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

Add resolve-propertyaccess test #864

Merged
merged 3 commits into from
Sep 23, 2019
Merged

Conversation

dcodeIO
Copy link
Member

@dcodeIO dcodeIO commented Sep 23, 2019

I recently noticed that there's something missing when resolving property accesses, so I added a test and found an issue with enum values. However, I think this still doesn't catch the issue I noticed initially which had something to do with resolving i32.MAX_VALUE somewhere. Going to investigate further.

@MaxGraey
Copy link
Member

Could you also fix this minor issue for namespace?

@dcodeIO
Copy link
Member Author

dcodeIO commented Sep 23, 2019

I think I found the initial issue, which happened for @lazy globals. Going to look into the other one :)

@MaxGraey
Copy link
Member

MaxGraey commented Sep 23, 2019

Hmm, but in that issue I don't use @lazy globals

@dcodeIO
Copy link
Member Author

dcodeIO commented Sep 23, 2019

Yeah, seems to be a different issue related to ctxElement being the start function in this case, not the namespace.

@dcodeIO dcodeIO merged commit 4a25bfa into master Sep 23, 2019
@dcodeIO dcodeIO deleted the resolve-propertyaccess-test branch November 8, 2019 01:59
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 this pull request may close these issues.

2 participants