Set abbreviated Node.type_name for long parameterized types

[erang20]

RDL parameterized types translate to Node.type that contains the list of parameters and their values. For example:

regfile some_regfile #(
    longint unsigned PARAM_A,
    longint unsigned PARAM_B,
) {
...
}

Might be instantiated as a Node with type_name = some_regfile_PARAM_A_200_PARAM_B_300

The list of parameters might be very long in some cases, so it would be helpful to add an option (e.g. max_node_type_param_lengh to abbreviate a long parameters list to a 32 bit hash hex, e.g. some_regfile_2d8fa187 instead of a very long type name.

[amykyta3]

Agree that type names can get pretty absurdly verbose. I have been noticing the same in some of the designs I have been involved in.

The current type name generation is actually according to what the SystemRDL spec defines (Section 5.1.1.4). I also extended the semantics for this to cover dynamic assignments.

I was actually thinking of addressing this in a similar way you suggested - to provide an option to generate shortened hashed type names. This is important since some languages that PeakRDL exports to may have a character limit on identifiers that is quite easy to reach with this behavior.

Since this is something that would be changed in the compiler, I will migrate this issue there.

[jeras]

In a documentation generator, hashes would not be the best option, they are not really intended to be human readable.

What I would like to see is an ordered list of all specializations of a parameterized type_name, so I could create a dictionary mapping long names to some iterator, like integers, roman numbers, letters of the alphabet, or a custom mapping defined by the user.