Open
Conversation
08ac92d to
1a4e30c
Compare
Collaborator
|
r? @nnethercote rustbot has assigned @nnethercote. Use |
- Implement handling of FnPtr TypeKind in const-eval, including: - Unsafety flag (safe vs unsafe fn) - ABI variants (Rust, Named(C), Named(custom)) - Input and output types - Variadic function pointers - Add const-eval tests covering: - Basic Rust fn() pointers - Unsafe fn() pointers - Extern C and custom ABI pointers - Functions with multiple inputs and output types - Variadic functions - Use const TypeId checks to verify correctness of inputs, outputs, and payloads
1a4e30c to
0983ccc
Compare
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
oli-obk
requested changes
Feb 5, 2026
| /// Compile-time type information about generic lifetimes. | ||
| #[derive(Debug)] | ||
| #[unstable(feature = "type_info", issue = "146922")] | ||
| pub struct Lifetime { |
Contributor
There was a problem hiding this comment.
This doesn't appear to be used anymore
| self.write_fn_ptr_type_info( | ||
| fn_ptr_place, | ||
| binder.skip_binder().output(), | ||
| signature.safety.is_unsafe(), |
Contributor
There was a problem hiding this comment.
You should exhaustively destructure signature so that future changes to the struct get picked up here.
|
|
||
| // FIXME: Merge with #151142 | ||
| // A general method to write an array to a static slice place. | ||
| fn project_write_array( |
Contributor
There was a problem hiding this comment.
Suggested change
| fn project_write_array( | |
| fn allocate_fill_and_write_slice_ptr( |
Or sth equally forcing ppl to read docs on what it does
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is for #146922.
Const-eval currently lacks full support for function pointer (fn) types. We should implement handling of FnPtr TypeKind, covering safe and unsafe functions, Rust and custom ABIs, input and output types, higher-ranked lifetimes, and variadic functions.