[3.2.13] Jadeite should support both legacy string comparison mode and unicode comparison mode

[ericwinger]

Based on Dale's comments, it sounds like this option should be turned on so Jadeite can support unicode method compilation. But need to wait until Rowan is ready to support unicode. https://github.com/GemTalk/Rowan/issues/877

[dalehenrich]

My guess is that it will be up to the user to on Unicode mode, but this is all premature … we need to understand all of the issues involved before moving forward

[dalehenrich]

I am not aware of the recommendations that make when folks decide to use Unicode source in topaz … and since topaz does not automatically turn on Université comparisons I don’t think Jadeite should either

[ericwinger]

fwiw - My simplistic tests show that nothing special needs to be done to save a method in topaz with a unicode character. So perhaps you're right that this isn't necessary (except to get around the comparison error encountered in the aforementioned comment?)

[ericwinger]

Correction - In topaz, when the method exists, compiling it again with a unicode string requires Unicode16 _useUnicodeComparePrimitives: true

[LisaAlmarode]

Retitle since unicode mode became (declaratively, not verified) required for 3.2.13 while everything isn't actually working. Waiting on 3.7 server issues with GsFilein.