You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to run some third-party code on Rhino 1.7.11 and noticed that Map and Set don't always behave as expected. Here are two test cases to reproduce the issue:
Due to the string concatenation, Rhino passes a ConsString instance to the NativeMap/NativeSet methods which is of course not equal to the String that was added to the collection initially.
Unlike #247 and #496 there's no obvious or intentional Java-interop here, so I hope this warrants a separate issue.
The text was updated successfully, but these errors were encountered:
I have been trying to run some third-party code on Rhino 1.7.11 and noticed that Map and Set don't always behave as expected. Here are two test cases to reproduce the issue:
Expected output:
value1
,17
| Actual output:undefined
,undefined
Expected output:
false
,true
,true
| Actual output:false
,false
,false
Due to the string concatenation, Rhino passes a ConsString instance to the NativeMap/NativeSet methods which is of course not equal to the String that was added to the collection initially.
Unlike #247 and #496 there's no obvious or intentional Java-interop here, so I hope this warrants a separate issue.
The text was updated successfully, but these errors were encountered: