Skip to content

Rewrite orchard.xref#382

Merged
alexander-yakushev merged 1 commit intomasterfrom
xref
Apr 7, 2026
Merged

Rewrite orchard.xref#382
alexander-yakushev merged 1 commit intomasterfrom
xref

Conversation

@alexander-yakushev
Copy link
Copy Markdown
Member

@alexander-yakushev alexander-yakushev commented Apr 7, 2026

Big redoing of orchard.xref that includes:

  • Improved performance.
  • Getting rid of eval (yikes).
  • Cleanup and compaction.

  • You've updated the changelog (if adding/changing user-visible functionality)

@alexander-yakushev alexander-yakushev force-pushed the xref branch 2 times, most recently from 1341e9f to 9d0c698 Compare April 7, 2026 09:58
@alexander-yakushev alexander-yakushev force-pushed the xref branch 2 times, most recently from 15423ce to e879854 Compare April 7, 2026 12:54
@bbatsov
Copy link
Copy Markdown
Member

bbatsov commented Apr 7, 2026

Thanks for looking into this! How did you even think of revisiting it?

I was wondering if the past if this is useful in its current state or no (and even considered replacing it with some xref that just uses regular expressions like swank-clojure did), but I guess it's better to have it than not to have it, and we're going to have it - it's better to optimize it. :-)

@alexander-yakushev
Copy link
Copy Markdown
Member Author

Just was cruising through the repo and found a namespace I haven't touched before:).

I'm not sure if anybody ever uses it, but now at least it's in a state that is not embarrassing to keep:).

@alexander-yakushev alexander-yakushev merged commit 51417b6 into master Apr 7, 2026
12 checks passed
@alexander-yakushev alexander-yakushev deleted the xref branch April 7, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants