Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0f3
Issue ID
997480
Regression
No
Unity incorrectly compares two values when the comparison method is written in F# and added to Unity through external DLL
How to reproduce:
1. Open the attached Unity project "fsharp-unity-test.zip".
2. Press "Play".
3. Check the results in the Console Window.
Expected result: all comparison tests succeed.
Actual result: some comparison tests fail.
Reproducible with - 2017.1.0a6, 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0b13, 2018.2.0a8
Could not test with - 5.6.0a1, 5.6.5p3, 2017.1.0a1, 2017.1.0a5 (Unity could not find the needed DLL)
Note:
The same problem occurs on 64-bit Windows, in MonoDevelop. Changing Unity External tools to Visual Studio or JetBrains Rider does not change the tests results.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment