-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[Java] Use Table's fully qualified path #8729
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
[Java] Use Table's fully qualified path #8729
Conversation
|
@nevi-me why the alias _Vector for Vector? |
|
Same reason; conflicts with user-defined types named @nevi-me I think this change might be missing our change to the code from |
|
@nevi-me this seems to be causing test failures, do you have possiblity to look at it? |
I'll take a look today, thanks |
|
the renaming to |
|
@aardappel Well, rather than complain about it, we're putting together this PR :) It's not a "possible name clash" for us, it's an actual name clash, and we have deployed code where renaming our Vector type is a really expensive change to make. What would you suggest as an alternative? |
|
Why not just fully qualify as with Table? |
|
"renaming our Vector type is a really expensive change to make" yes, that's just what I said about making the change on the FlatBuffers side. Except it is 1 user (you) vs potentially many FlatBuffers users affected, depending on how this collision gets fixed. Maybe first lets understand the problem. How is your custom vector type set up in a way that it collides with these FlatBuffers Vector types, and why is that unavoidable? Agree with @bjornharrtell that in theory this should all be solvable with qualifying. |
It's a table type called |
I'm not convinced of rename of Vector.
|
it seems there is some overlap with this PR and #8581 |
Yes, because @aardappel said if #8581 was four PRs it would be easier to review, and there's been no other maintainer activity on it, so @nevi-me helped me split it up in the hopes that we could get these changes accepted and merged so that we don't need to keep as many local patches. It's not so much "some overlap" as it is #8581 that's been broken up. |
|
Thank you for the context @maxburke ! I was just going through all the open PRs and noticed that. |
When a table's name is called `Table`, the Java bindings generated result in an error due to there being 2 Tables. This fixes the issue by fully qualifyng the flatbuffers Table import.
2b3c88a to
d9ccb92
Compare
|
I'm looking at the failures here, trying to reproduce them locally. I'm seeing a lot of stray changes when I run the formatting scripts, I'm checking if maybe I have a different clang version or something. |
bjornharrtell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see this now only does what it says it does, which I think is fine.
What I missed is that I have to build |
|
@aardappel consider for merge |
|
this also LGTM - since tests pass I'm going to ship it. |
|
A bit messy that this is an exception to all the other things in the |
When a table's name is called
Table, the Java bindings generated result in an error due to there being 2 Tables. This fixes the issue by fully qualifyng the flatbuffers Table import.Fixes #8728