Menu

#203 Detector for narrowing conversion on numeric types

3.x
closed-rejected
None
4
2017-10-22
2009-04-12
ilya katz
No

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

Discussion

  • ilya katz

    ilya katz - 2009-04-12
     
  • ilya katz

    ilya katz - 2009-04-12
    • summary: suggeted solution for feature request 2617667 --> suggested solution for feature request 2617667
     
  • ilya katz

    ilya katz - 2009-04-12
    • priority: 5 --> 4
     
  • ilya katz

    ilya katz - 2009-04-12
    • priority: 4 --> 5
     
  • William Pugh

    William Pugh - 2009-08-04

    Do you have any experience with how often this problem arises?

    Bill

     
  • William Pugh

    William Pugh - 2009-08-04
    • priority: 5 --> 4
    • assigned_to: nobody --> wpugh
    • status: open --> open-accepted
     
  • ilya katz

    ilya katz - 2009-09-23

    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

     
  • Andrey Loskutov

    Andrey Loskutov - 2014-06-19

    Please provide the patch on latest git state.

     
  • Andrey Loskutov

    Andrey Loskutov - 2014-06-19
    • summary: suggested solution for feature request 2617667 --> Detector for narrowing conversion on numeric types
    • status: open-accepted --> pending
    • Group: --> 3.0.1
     
  • Andrey Loskutov

    Andrey Loskutov - 2017-10-22
    • Status: pending --> closed-rejected
     

Log in to post a comment.