josh11bandJosh L b25117b508 Do not resolve the declaration when forming a specific for use in an eval block (#4692) ...

When substituting into a generic in order to form a generic eval block,
we form `SpecificId`s to track the list of arguments that should
eventually be used to form a specific referenced by the eval block.
Values within that specific are not needed and won't ever be used, so
it's safe to skip forming them in the first place.

Co-authored-by: Josh L <josh11b@users.noreply.github.com>

2024-12-17 00:39:48 +00:00

..

no_prelude

Do not resolve the declaration when forming a specific for use in an eval block (#4692)

2024-12-17 00:39:48 +00:00

deduce.carbon

Do not resolve the declaration when forming a specific for use in an eval block (#4692)

2024-12-17 00:39:48 +00:00

fail_todo_param_in_type.carbon

Model Core.Int as a class type (#4644)

2024-12-16 22:19:23 +00:00

redeclare.carbon

Do not resolve the declaration when forming a specific for use in an eval block (#4692)

2024-12-17 00:39:48 +00:00

resolve_used.carbon

Model Core.Int as a class type (#4644)

2024-12-16 22:19:23 +00:00

return_slot.carbon

Do not resolve the declaration when forming a specific for use in an eval block (#4692)

2024-12-17 00:39:48 +00:00

undefined.carbon

Model Core.Int as a class type (#4644)

2024-12-16 22:19:23 +00:00