This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 228
K Desktop CLR runtime behaves different on string comparison options than core runtime and windows console app #600
Comments
Probably something to do with how we're configuring the CLR host. |
For ease, project.json for VS2015 preview is:
|
Do we need to file this in CoreCLR issue tracking system? |
It's internal bug 1017568, which CoreCLR team didn't find problem and believe is our host problem. |
This issue still can be repo today. |
@troydai Can you try this with your hacked up code to pass Culture across threads? /cc: @DamianEdwards |
Test application: The full comparison across DNX451, DNXCORE50 and Desktop .Net 4.5.1:
|
@troydai was this with your hack? in other words, does it still fail to the proper comparison with your hack? |
It's not hacking. I'm working on the results after apply #953 changes. |
Merged
Fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Was using VS14 CTP3
Actual:
The code generate the same result under the following:
But the code generate the wrong result in
K run (under desktop CLR using kvm)
Here's the code
Here's the result diff
The original order of the list entries...
0x49
0x69
0x131
Invariant culture...
0x69
0x49
0x131
Invariant culture, ignore case...
Desktop CLR:
Core CLR:
The current culture is "en-US".
Current culture...
0x69
0x49
0x131
Current culture, ignore case...
Desktop CLR:
Core CLR:
Ordinal...
0x49
0x69
0x131
Ordinal, ignore case...
Desktop CLR:
Core CLR:
Turkish culture, ignore case...
Desktop CLR:
Core CLR:
Expected:
Desktop CLR and Core CLR result should be the same
The text was updated successfully, but these errors were encountered: