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

Parent definitions in JniT use the derived Class information. #329

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Aug 4, 2024

Parent definitions in JniT use the derived Class information.

I believe this is necessary for inheritance to work with class loaded objects properly.

Also, ParentT has been renamed to ParentJniT to disambiguate from ParentT when used in relation to a class (i.e. ParentJniT refers to the JniT of the ParentT).

@copybara-service copybara-service bot changed the title Parent definitions in JniT use the derived class information. Parent definitions in JniT use the derived Class information. Aug 4, 2024
@copybara-service copybara-service bot force-pushed the test_659313649 branch 3 times, most recently from 2569b68 to cd18b45 Compare August 5, 2024 17:18
I believe this is necessary for inheritance to work with class loaded objects properly.

Also, `ParentT` has been renamed to `ParentJniT` to disambiguate from `ParentT` when used in relation to a class (i.e. `ParentJniT` refers to the `JniT` of the `ParentT`).

PiperOrigin-RevId: 659597301
@copybara-service copybara-service bot merged commit 1db024f into main Aug 5, 2024
1 check passed
@copybara-service copybara-service bot deleted the test_659313649 branch August 5, 2024 17:25
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.

1 participant