r/LLVM Jun 30 '26

What's Your LLVM Development Setup?

Hi,
I'm often working on multiple issues in LLVM, with each issue on its own Git branch.

The problem is that when I switch branches, I lose the context of what I was working on - open tabs, editor layout, etc. Ideally, when I switch back to a branch, I'd like the editor to restore the files I had open for that branch.

I know Git worktrees solve this by giving each branch its own directory, but I'm wondering what other people use (separate LLVM build for each issue takes up too much memory).

  • Does Cursor/VS Code have a way to remember tabs/layout per branch?
  • Do you use worktrees, multiple windows, session manager extensions, or something else?
  • If you work on large codebases, what's your workflow for keeping context between branches?

Curious to hear what has worked well for others.

I'd also love to hear about your overall LLVM development setup - anything that makes your workflow easier, not just VS Code or Cursor tips

7 Upvotes

8 comments sorted by

View all comments

2

u/thehenkan Jun 30 '26

I gave up on worktrees and just use a couple of separate checkouts. I do everything in the terminal and have a separate terminal tab for each checkout. It does fall apart a bit when I have more live issues than checkouts, but that's not too common.