16 character suffix in cargo executable output names


The output of cargo is as show in the pic. Can you please point me to how those 16 hex character suffixes (highlighted in the pic) are generated? Is it some hash of the file contents?


It's a fingerprint generated by Cargo here:

1 Like