Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007524OCamltypingpublic2017-05-02 12:012017-05-02 12:08
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0007524: Add warning when using '=' in for none immediate values
DescriptionThis is a proposal/request for creating a warning that will be trigger when using '=' on any value that is not immediate (like lists, records).

The main motivation is to avoid problems as the ones described in the reports 0003921, 0007502.

We were also affected in our product by this behavior. The problem that we had was that an algorithm using 'compare a b = 0' was changed to 'a = b'. This produced a big performance degradation since we were not aware that '=' didn't performed physical comparison.

When enabling this warning new programmers will be notified of this behavior therefore avoiding the unintended consequence.
TagsNo tags attached.
Attached Files

- Relationships
related to 0007502resolvedfrisch (=) does not use physical equality unlike compare 
related to 0003921acknowledged structural equality for cyclic data structure cannot be interrupted 

-  Notes
dra (developer)
2017-05-02 12:05

It's hard at the moment to imagine our being able to turn this warning on by default, I think, so the benefit to new users may be harder to achieve. That doesn't detract from the benefit of having the warning, though.

- Issue History
Date Modified Username Field Change
2017-05-02 12:01 modlfo New Issue
2017-05-02 12:05 dra Note Added: 0017759
2017-05-02 12:06 dra Relationship added related to 0007502
2017-05-02 12:07 dra Relationship added related to 0003921
2017-05-02 12:08 dra Status new => acknowledged

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker