BCW0020: WARNING: Assignment made to same expression. Did you mean to assign to something else?
BCW0021: WARNING: Comparison made with same expression. Did you mean to compare with something else?
Should issue:
BCW0020: WARNING: Assignment made to same expression. Did you mean to assign to something else?
BCW0021: WARNING: Comparison made with same expression. Did you mean to compare with something else?
I have patch ready but I have some weird problem when building PatternMatching (and PatternMatching only, ie. Extensions and Useful build fine for instance) :
I've changed ast.model.boo to set explicit values to BinaryOperatorType such as we can have a BinaryOperatorMask enum in order to more efficiently compare an operator to an operator group/kind (instead of a flurry of "|| ... ||").
For some reason PatternMatching build fails cause it seems to use the old values before that change but I cannot see how and why is it the only one to do this. Any ideas??
Cedric Vivier added a comment - 20/Jan/09 04:37 AM I have patch ready but I have some weird problem when building PatternMatching (and PatternMatching only, ie. Extensions and Useful build fine for instance) :
I've changed ast.model.boo to set explicit values to BinaryOperatorType such as we can have a BinaryOperatorMask enum in order to more efficiently compare an operator to an operator group/kind (instead of a flurry of "|| ... ||").
For some reason PatternMatching build fails cause it seems to use the old values before that change but I cannot see how and why is it the only one to do this. Any ideas??
Improvement
Resolved
Minor
WARNING: Assignment/Comparison made to/with same expression.
I have patch ready but I have some weird problem when building PatternMatching (and PatternMatching only, ie. Extensions and Useful build fine for instance) :
I've changed ast.model.boo to set explicit values to BinaryOperatorType such as we can have a BinaryOperatorMask enum in order to more efficiently compare an operator to an operator group/kind (instead of a flurry of "|| ... ||").
For some reason PatternMatching build fails cause it seems to use the old values before that change but I cannot see how and why is it the only one to do this. Any ideas??