Skip to content

ctypes::void still isn't correct #1907

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Feb 26, 2012 · 0 comments
Closed

ctypes::void still isn't correct #1907

brson opened this issue Feb 26, 2012 · 0 comments

Comments

@brson
Copy link
Contributor

brson commented Feb 26, 2012

This type is intended to only be used as an opaque type for unsafe pointers to point to. It is defined in a way that isn't constructable or destructurable, but it is still a copyable type. That means that you can define type complicated_c_struct = ctypes::void with the intent of using it only as an unsafe pointer, but could potentially write let newcopy = *complicated_c_struct_pointer and create a big mess.

We could put a resource field inside it to prevent this.
@ghost ghost assigned lht Mar 8, 2012
@graydon graydon closed this as completed in ab4105d Apr 5, 2012
@brson brson unassigned lht Jun 16, 2014
@GKFX GKFX mentioned this issue Jul 16, 2022
Merged
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval
Remove github action version check (rust-lang#1907)
50d26b6 
We currently have a circular dependency. The action repository cannot be on the same version as Kani by the time we run the release workflow.

The github action CI enforces that the tracking version has been released. So we can't really update the github action until the release is complete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@graydon @lht @brson