Bug 550836 - Provide a warning for always-true or never-true numeric literal conditions
Summary: Provide a warning for always-true or never-true numeric literal conditions
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-06 07:01 EDT by Nobody - feel free to take it CLA
Modified: 2023-08-18 13:05 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nobody - feel free to take it CLA 2019-09-06 07:01:48 EDT 
This bug originally came from this reply to a java puzzle I made https://twitter.com/nichijou_lab/status/1169247267569590272

Basically if you have a condition similar to the one above - e.g. byte b <128 or byte b >=128 we could add a warning that says it is always the case or never the case.

It doesn't necessarily need to be bounded to the byte type but can be extended for other numericals also.
Comment 1 Eclipse Genie CLA 2021-08-27 16:09:14 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-08-18 13:05:09 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.