Handling of multiple declaration/meanings of the same interrupt vector

[trembel]

This solves #17.
Interrupts of the newer AVR MCUs having multiple name, e.g. the TCA interrupts of the attiny412:

        ...
        <interrupt index="8" module-instance="TCA0" name="LUNF"/>
        <interrupt index="8" module-instance="TCA0" name="OVF"/>
        <interrupt index="9" module-instance="TCA0" name="HUNF"/>
        <interrupt index="10" module-instance="TCA0" name="CMP0"/>
        <interrupt index="10" module-instance="TCA0" name="LCMP0"/>
        ...

will be stored as TCA0_LUNF_OVF, respectively TCA0_CMP0_LCMP0.

[Rahix]

I can't say that I am a big fan of this ad-hoc string manipulation because it's very fragile ... But I cannot think of a different solution that does not require bigger changes, so I guess it is fine. We won't see this 'duplicate interrupt' situation too often anyway, I hope.

[trembel]

Same for me. The other option would have been adding a "module-instance" field to the interrupt struct, but than serialization would not work (or needs to exclude the module-instance). This would give a much simpler string manipulation.

[trembel]

I saw now that you do the serialization manually, so actually then an additional field in the interrupt struct would not change anything?

Then we could add a field module-instance as Option<std::string::String>, and in chip.rs we could append name with module-instance if it exists, and append also the other module-instance in case of duplicate index number.

[trembel]

this change would then combine #19 with #20.

[Rahix]

Let's keep it like it is for now and only fix it if it breaks for someone ;) No point wasting too much effort on this rare issue ...

[Rahix]

Thanks a lot!