I am using trienet within my UWP App, however I had to remove all the calls to string.Intern() (here and here), and replace them by simple string assignements such as m_Origin = origin, because the .NET team decided to remove methods which they "regretted adding in the first place, or restricted our plans around innovating for the future." (according to David Kean).
However, I'm guessing this has a negative impact on performance. Is there anyway to limit this?
I am using trienet within my UWP App, however I had to remove all the calls to
string.Intern()(here and here), and replace them by simple string assignements such asm_Origin = origin, because the .NET team decided to remove methods which they "regretted adding in the first place, or restricted our plans around innovating for the future." (according to David Kean).However, I'm guessing this has a negative impact on performance. Is there anyway to limit this?