Stable type identifiers: a missing piece for crABI and export

I hadn't thought of that before and you are right. Hygienic macros create different objects that have the same path but are stored as different objects in the compiler. For the time being, I have no definitive answer. In this case, would the existing hygiene information that the compiler tracks internally be enough to determine which is which in the hash? Or would a completely different method be needed?