Repository navigation
fix(JFace M3): preserve explicit refresh callbacks on merged master queue - #42
Merged
Merged
Conversation
…erged deadline Receive exactly two original Eclipse Java postimages from canonical Synexia source-sealed #12917; retain existing JFace, SWT and M3 array lanes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original Eclipse/JFace receiver — master-forward, source sealed
This is a two original FILE refinement on current
master@c5526df429f908a246cde6f71f8ce32db5f97fcc, not wholesale integration of dirtydevelopPR #37. The exact output was authored first as Maven/OpenRewrite source-pinned Java/test stages in canonical Synexia #12917 commit880d37f93032d1be152c39fb57605052b89d6eaf.M3Viewers.java: preserve Reconcile JFace viewer queue and iterative tree search without losing merged M3 array lanes #36 monotonic first-post nanoTime deadline and stale-timer generation/batch isolation, worker-safe owning Display, selection and array-backed viewer delta implementation; only consecutive dedicatedrefreshLaterrequests to the identical target can coalesce. Explicitpost(... M3ViewerDelta.refresh(...))operations remain separate and ordered. No external M3+JDK layer or changed public descriptors.M3ViewersTest.java: original native JUnit5explicitRefreshPostsRetainCardinalityAcrossDebouncedRefreshLaterproves two adjacent dedicated refreshLater coalesce once while two explicit refresh posts plus a later refreshLater remain separately observable (expected total 4).M3ViewerDelta.java, iterative TreeViewer or Project Explorer Project Explorer: receive original worker-safe resource deltas and M3 opt-in path #38 original sources.2ee741c25d27fb3b04bedafd6ad7c9ba08efff865c3b749b883a6466d534437a→cc4ebcc4805c93b49a3afd6db29bc2a2926200e9d6f7eaf981d3861166862973; test24ef327022bb707e624686f153d9d3a51cbc6f34a57332367e30a7cac35abe7f→1df4406ab5a6dd6e764872a4960d5f0faae9665e8be7c832d99e50a9d0e5286c.Qualification
Executed locally: standalone Java21
javac --release 21 -Xlint:all -Werrorand 2,396,745 exhaustive 0–7-event queue-model checks PASS. Not the native Eclipse class. Not run: exact GitHub master-head SWT/JFace native test, Maven/OpenRewrite SDK test, Tycho/JDT/PDE reactor, native GTK/Win32/Cocoa UI/pixels or installed M3JDK21/JNI qualification. Keep draft until those exact-head gates succeed; do not report completion or auto-merge.