Jonah Graham 48156b4653 Bug 572594: Avoid using generic Consumer interface ... Using the Consumer interface means that code navigation is substantially harder. e.g. open ImportMemoryDialog and do a call hierarchy on who calls scrollRenderings. You end up in Consumer.accept, which (naturally) has 100s of callers, so identifying which ones are relevant is very difficult. Change-Id: I8817568e992955d5b01a591a9cffb2447b9e5008		2021-04-06 13:06:25 -04:00
..
org.eclipse.cdt.debug.core.memory	Bug 572594: Avoid using generic Consumer interface	2021-04-06 13:06:25 -04:00
org.eclipse.cdt.debug.core.memory.tests	Bug 572594: Avoid using generic Consumer interface	2021-04-06 13:06:25 -04:00
org.eclipse.cdt.debug.ui.memory-feature	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00
org.eclipse.cdt.debug.ui.memory.floatingpoint	Bug 566511: [releng] Add missing UTF-8 encoding for all CDT projects	2020-08-30 20:02:41 -04:00
org.eclipse.cdt.debug.ui.memory.memorybrowser	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00
org.eclipse.cdt.debug.ui.memory.search	Bug 566511: [releng] Add missing UTF-8 encoding for all CDT projects	2020-08-30 20:02:41 -04:00
org.eclipse.cdt.debug.ui.memory.traditional	Bug 568728: Drop execute permission on files	2020-11-18 17:38:22 +01:00
org.eclipse.cdt.debug.ui.memory.transport	Bug 572594: Avoid using generic Consumer interface	2021-04-06 13:06:25 -04:00
pom.xml	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00