forked from dotnet/Silk.NET
-
Notifications
You must be signed in to change notification settings - Fork 0
[Do not merge] Diff name changes branch with develop/3.0, with noise removed #20
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
Draft
Exanite
wants to merge
194
commits into
develop/3.0-diff
Choose a base branch
from
feature/vulkan-bindings-3.0-improvements-diff
base: develop/3.0-diff
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[Do not merge] Diff name changes branch with develop/3.0, with noise removed #20
Exanite
wants to merge
194
commits into
develop/3.0-diff
from
feature/vulkan-bindings-3.0-improvements-diff
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This looks like it's from some sort of built-in renamer. Don't think we'll ever use this since we have a custom renamer.
… work with native name attributes
Not sure why these were not being coerced when the Vulkan PR was merged, but they started getting coerced in this PR. This technically is a good thing since it means the coerce backing types code is now working as previously intended. However, the previously intended implementation missed an edge case, which this commit fixes.
This is because the structs were impossible to reasonably construct before.
VaListTagHandle is an extra handle struct that seems to generate on Linux (and not on Windows) and breaks global prefix determination.
OpenAL: ContextErrorCode seems to always be replaced with ErrorCode, even on Windows. Not sure why. This also happened during the last PR, but I didn't commit it.
…name trimmer code
Honestly, what I wrote is a complete guess, I'll likely revisit these once I understand them more.
The functionality this method contains seems heavily duplicated. I will likely update existing code in a later commit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Github is shows the wrong diff for this PR
Github seems to be diffing
feature/vulkan-bindings-3.0-improvements-diffwith the commit right before the head ofdevelop/3.0-diff, likely because of the merge conflict that is showing at the bottom of this PR.I suggest diffing the PR locally.
This PR contains the changes for dotnet#2503, but with a lot of the noise removed.
This PR is designed to emphasize the name-related changes, so changes like the attribute changes and enum member value rewrite changes are removed to make the name-related changes easier to review.