Skip to content

Debug info for const generics is hashes rather than something nice #115786

Open

Description

In #115748 I got a test failure in tests/debuginfo/function-names.rs: function_names::const_generic_fn_non_int<{CONST#ad91263f6d2dd96e}> changed to static fn function_names::const_generic_fn_non_int<{CONST#73a38766b652ae7d}>. That PR leads to some new AllocIds being generated which shifts some IDs around, so it seems like the AllocId are affecting the function name here. @oli-obk was confused by this since with valtrees, shouldn't our function names be stable now? Indeed AllocId are not very stable at all so it seems potentially problematic if they are relevant for function names. The underlying function call is const_generic_fn_non_int::<{ () }> so this is not a very complicated valtree. ;)

Cc @rust-lang/project-const-generics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-const-genericsArea: const generics (parameters and arguments)F-adt_const_params`#![feature(adt_const_params)]`F-const_generics`#![feature(const_generics)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-typesRelevant to the types team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions