-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Split Position from Location type hierarchy #10061
base: feature/bytecode-modification
Are you sure you want to change the base?
Split Position from Location type hierarchy #10061
Conversation
patches/api/0449-Split-Position-from-Location-type-hierarchy.patch
Outdated
Show resolved
Hide resolved
340a97b
to
77180b3
Compare
ad1dacb
to
f63f5c0
Compare
So I did a bit more converting methods and as you can see the diff has grown quite a bit. I'm starting to get hesitant to do this for more than methods with Location that we add. One downside of not doing it all at once is it makes it slightly more annoying to work with the API before its all converted since its 2 different types. EDIT: decided to scale back this PR to only removing Position from the Location type hierarchy and rewriting the several methods that already take Position as a parameter. |
a607689
to
d75b6c5
Compare
b9544bf
to
f545498
Compare
d75b6c5
to
b7e37d7
Compare
f545498
to
8696a8c
Compare
6549dc8
to
be4a567
Compare
8696a8c
to
31f14a2
Compare
be4a567
to
06fcb36
Compare
31f14a2
to
33039cd
Compare
06fcb36
to
5d35f62
Compare
33039cd
to
f10858e
Compare
5d35f62
to
aa08956
Compare
This is how the bytecode modification framework from #10060 is used to
replace some parameter types with Position andmake Location not implement Position anymore. The test plugin is setup to compile against current paper api and show that there are no compat breaks.