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

Implement standard traits on C-unwind ABI function pointers #100

Closed
lopopolo opened this issue Sep 10, 2022 · 3 comments
Closed

Implement standard traits on C-unwind ABI function pointers #100

lopopolo opened this issue Sep 10, 2022 · 3 comments
Labels
ACP-accepted API Change Proposal is accepted (seconded with no objections) api-change-proposal A proposal to add or alter unstable APIs in the standard libraries T-libs-api

Comments

@lopopolo
Copy link

Proposal

Implement the standard set of core traits on C-unwind ABI function pointers:

Problem statement

I would like to stabilize RFC rust-lang/rfcs#2945 which has tracking Issue rust-lang/rust#74990. Implementing common traits like fmt::Debug on these function pointers is blocking stabilization of the c_unwind feature.

Motivation, use-cases

The lack of common traits like fmt::Debug on C-unwind ABI function pointers prevents them from being used with common tools like bindgen.

Solution sketches

rust-lang/rust#101263 has been filed and signed off on by the compiler team.

Links and related work

What happens now?

This issue is part of the libs-api team API change proposal process. Once this issue is filed the libs-api team will review open proposals in its weekly meeting. You should receive feedback within a week or two.

@lopopolo
Copy link
Author

I was asked to file this ACP by @thomcc here: rust-lang/rust#101263 (comment).

@lopopolo
Copy link
Author

lopopolo commented Oct 7, 2022

Hi folks, checking in on this ACP since its been about 4 weeks since I opened it and the rustc dev guide and ticket template hinted that this would be looked at within a week or two.

This ACP is (I think) blocking the addition of some fmt traits as part of an already accepted RFC. Is there a part of the process I've missed?

I'm still not quite sure why this change (which is part of a larger, already-approved RFC) is blocked on an ACP. It looks like some API changes, like rust-lang/rust#101308, can make it to nightly without one.

@joshtriplett is this ACP something you can help me get some eyes on? (I saw you approved the new API addition I linked)

@lopopolo
Copy link
Author

rust-lang/rust#101263 is approved and in the bors queue, which I think means this ACP is not required anymore.

@dtolnay dtolnay added the ACP-accepted API Change Proposal is accepted (seconded with no objections) label Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ACP-accepted API Change Proposal is accepted (seconded with no objections) api-change-proposal A proposal to add or alter unstable APIs in the standard libraries T-libs-api
Projects
None yet
Development

No branches or pull requests

2 participants