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

Properly represent final on classes and fields #7381

Merged
merged 10 commits into from
Sep 4, 2018

Conversation

Simn
Copy link
Member

@Simn Simn commented Sep 4, 2018

This pull requests

  1. supports final class and
  2. cleans up final on fields by properly representing it in cf_final.

I've decided to do this properly instead of juggling @:final metadata around. This means some macros might have to adapt.

See #6584

@Simn Simn merged commit ff7e220 into HaxeFoundation:development Sep 4, 2018
@Simn Simn deleted the proper_final branch September 4, 2018 11:41
@ncannasse
Copy link
Member

One extra refactoring that might be worth is to store booleans into a single bit flag (cf_public/cf_extern/cf_final) : it will save a few bytes of memory per class field which is quite good, and also allows us to add additional flags without breaking macros etc.

Same remark for tclass

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.

None yet

2 participants