here is my attept to warn for code that can result in wrong values when performing narrowing conversion. it can probably be extended to include other types that have similar problems
It happened twice in the development team that I am working in, but it took a significant time to to actually find where the problem was (which prompted me to submit the bug). So, although not frequent, it seems to me that it is worth to be added to eliminate the headache that it can bring
Ilya
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you have any experience with how often this problem arises?
Bill
It happened twice in the development team that I am working in, but it took a significant time to to actually find where the problem was (which prompted me to submit the bug). So, although not frequent, it seems to me that it is worth to be added to eliminate the headache that it can bring
Ilya
Please provide the patch on latest git state.