You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Of course, this is a combination of multiple issues (#8 - my personal most wanted issue :-)), but it also shows that hard-coded line-break intervals might be an imperfect strategy when creating diffs. Probably PoppyPrint should support a separate diff mode where two source codes are compared based on their ASTs first and a diff is generated afterward? Or would this be out of scope for PoppyPrint?
The text was updated successfully, but these errors were encountered:
I just stumbled into a situation where traditional diffs are easier to read than pretty diffs:
From:
To:
Traditional diff:
installPreviewDependenciesForTests ^ self installPreviewDependencies: { self depInbox: 'SUnit-ct.125'. "TestCase>>#runCaseWithoutTimeout for SandboxKernelTest" self depInbox: 'SUnit-ct.132'. "TestCase>>#assert:equals:description: with lazy descriptions" - self depInbox: 'Kernel-ct.1407'. "Fixes Context >> #isPrimFailToken: for ProtoObjects" }
Poppy-printed diff:
Of course, this is a combination of multiple issues (#8 - my personal most wanted issue :-)), but it also shows that hard-coded line-break intervals might be an imperfect strategy when creating diffs. Probably PoppyPrint should support a separate diff mode where two source codes are compared based on their ASTs first and a diff is generated afterward? Or would this be out of scope for PoppyPrint?
The text was updated successfully, but these errors were encountered: