-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Nicer printing of type and region variables #2632
Copy link
Copy link
Closed
Labels
A-prettyArea: Pretty printing (including `-Z unpretty`)Area: Pretty printing (including `-Z unpretty`)C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Metadata
Metadata
Assignees
Labels
A-prettyArea: Pretty printing (including `-Z unpretty`)Area: Pretty printing (including `-Z unpretty`)C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Today on IRC several of us were talking about how the way that type variables and region variables are printed (
<VN>and<RN>, respectively, whereNis an id number) is rather ugly. Now that we have integral type variables, printing them as<VIN>(as is happening now) just adds insult to injury. "integer" and "unconstrained int" were suggested as nicer solutions for integral type variables. We should come up with something nicer for the others as well.There's already a
-Z ppregionscompiler flag, useful for debugging, that prints the IDs of regions. Maybe there could be a-Z ppvaridsflag that prints the ID numbers for times when we really need them.