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

Problem: renaming types at the C header layer is not possible #17

Closed
2 tasks done
danielhenrymantilla opened this issue Jun 10, 2020 · 1 comment
Closed
2 tasks done
Assignees
Labels
K-feature Kind: proposed new code to implement new behaviour

Comments

@danielhenrymantilla
Copy link
Collaborator

danielhenrymantilla commented Jun 10, 2020

Support renaming the types (at the C header layer) for:

  • Opaque types.

    • Syntax: #[ReprC::opaque("name_in_the_c_header")]
  • everything else

    • Idea of the syntax: #[ReprC::rename("name_in_the_c_header")]

      • would probably override the syntax for opaque types for the sake of consistency

      • #[derive_ReprC(rename = "...")] would also be possible, but the ::syn-less equivalent of the ReprC! { ... } macro would then be left out.

@danielhenrymantilla danielhenrymantilla added K-feature Kind: proposed new code to implement new behaviour soon-ish labels Jun 10, 2020
@danielhenrymantilla danielhenrymantilla added this to the Version 0.1.0 milestone Jun 10, 2020
@steph-lui steph-lui removed this from the Version 0.1.0 milestone Jan 31, 2022
@steph-lui steph-lui added 2022-Q2 and removed 2022-Q1 labels Apr 4, 2022
@danielhenrymantilla
Copy link
Collaborator Author

Completed as per the latest safer-ffi changes. Demo:

TODO: release to crates.io

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
K-feature Kind: proposed new code to implement new behaviour
Projects
None yet
Development

No branches or pull requests

2 participants