Add an environment variable for dumping type IDs #11168
Merged
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.
If the environment variable
CRYSTAL_DUMP_TYPE_ID=1
is present, instructs the compiler to print a dump of every type with its type ID bounds; the upper bound is the type'scrystal_instance_type_id
, and the lower bound is the minimumcrystal_instance_type_id
of its subtypes. (The bounds are used byis_a?
on virtual types.) This is used to generate the type ID dumps in #11167. For a blank program with the empty prelude, the dump looks like:Some generic metaclasses above are uninstantiated (like
Tuple(*T).class
), so they should not contain the generic parameters. This is handled by #11104.This is mostly for quickly debugging the compiler itself, similar to
DUMP
andAFTER
, so there are no specs.