Bug 560247 - Support all functional expressions in debugger expressions / snippets
Summary: Support all functional expressions in debugger expressions / snippets
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.15   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 560248 560249 560250
Blocks: 560626
  Show dependency tree
 
Reported: 2020-02-17 20:26 EST by Jesper Moller CLA
Modified: 2024-02-16 02:03 EST (History)
2 users (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 Jesper Moller CLA 2020-02-17 20:26:39 EST 
This is an umbrella bug to catch all outstanding issues around debug expressions containing functional expressions (and, ideally, also inner classes).
Comment 1 Eclipse Genie CLA 2022-02-21 17:24:52 EST 
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 Sarika Sinha CLA 2022-02-21 22:50:45 EST 
@Gayan,
Will you be able to evaluate what is missing and what is fixed?
Comment 3 Gayan Perera CLA 2022-02-22 15:35:56 EST 
@Sarika sure i can have look at it for 4.24 release
Comment 4 Sarika Sinha CLA 2022-02-23 01:11:37 EST 
(In reply to Gayan Perera from comment #3)
> @Sarika sure i can have look at it for 4.24 release

Thanks!
Comment 5 Eclipse Genie CLA 2024-02-16 02:03:06 EST 
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.