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

feat: native input output data #312

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Conversation

andywiecko
Copy link
Owner

Introduce NativeInputData and NativeOutputData to eliminate ambiguity between andywiecko.BurstTriangulator.Input/OutputData<T> and andywiecko.BurstTriangulator.LowLevel.Unsafe.Input/OutputData<T>. The latter, located in LowLevel.Unsafe, have now been marked with the Obsolete attribute and includes an implicit cast to the newly introduced NativeInputData and NativeOutputData.

Introduce `NativeInputData` and `NativeOutputData` to eliminate ambiguity between `andywiecko.BurstTriangulator.Input/OutputData<T>` and `andywiecko.BurstTriangulator.LowLevel.Unsafe.Input/OutputData<T>`. The latter, located in `LowLevel.Unsafe`, have now been marked with the `Obsolete` attribute and includes an implicit cast to the newly introduced `NativeInputData` and `NativeOutputData`.
@andywiecko andywiecko merged commit e090f05 into main Jan 16, 2025
6 checks passed
@andywiecko andywiecko deleted the feat/native-input-output-data branch January 16, 2025 11:03
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