-
-
Notifications
You must be signed in to change notification settings - Fork 393
ExprSkull - Breaking Change #7904
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
base: dev/feature
Are you sure you want to change the base?
ExprSkull - Breaking Change #7904
Conversation
this seems a bit more breaking than is really necessary |
Well the lack of discussion in the issue didn't really point towards changing |
Gotcha |
I'm neutral, either or. |
Being the one who made the issue I'll at least give my perspective. As I said on the issue either or I personally push towards ExprSkull more than ExprEyeLocation, but I also know I see |
Moving this to dev/feature due to breaking changes |
I don't think I love making the |
So the current count seems to be So I'll change this PR to change |
Problem
ExprEyeLocation
andExprSkull
has a pattern confliction ofhead of ...
which could lead to the retrieval of the wrong expression depending on the use case.Solution
This PR fixes this confliction by removing the option of
head
inExprSkull
Thus allowing users to be able to retrieve the exact expression/return type they desire.
Is a breaking change.
Testing Completed
N/A
Supporting Information
N/A
Completes: #7837
Related: none