Comment 1 for bug 1847159

I can't really see INTERN as something that any of the developers could devote time to improving.

More likely, we should speed up string comparison, and also not compute hashes using all character in a string. Perhaps the leading 8 chars and trailing 8 chars will contain enough entropy, with the full string= to deal with collision resolution. So while I see this special-case request as a wont-fix, it would definitely be interesting to see the performance tradeoff of purposely worse hashes, in the hope of spending less time doing it, provided we also have a faster comparator.

(and if we had feedback-directed optimization, it had best be more general than to speed up INTERN)