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

refactor: avoid using unsafe code where possible #5

Closed
wants to merge 1 commit into from

Conversation

sarah-quinones
Copy link

this is essentially a full rewrite of concrete-fft.
by depending on the bytemuck crate (which is a very lightweight and heavily tested dependency), and with the new PodStack abstraction from dyn-stack (which we already depend on) to avoid dealing with uninitialized memory, we can avoid over 99% of the unsafe code usage in concrete-fft.

@sarah-quinones sarah-quinones force-pushed the safety-refactor branch 2 times, most recently from 596c663 to 9e917c5 Compare March 1, 2023 13:18
src/x86.rs Outdated Show resolved Hide resolved
@sarah-quinones sarah-quinones force-pushed the safety-refactor branch 2 times, most recently from 7ae71a7 to 0bc3404 Compare March 3, 2023 13:51
Copy link
Member

@IceTDrinker IceTDrinker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot! We'll see how it behaves once we plug it in!

@sarah-quinones
Copy link
Author

superseded by #9

@IceTDrinker IceTDrinker deleted the safety-refactor branch March 16, 2023 14:02
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.

2 participants