Skip to content

Conversation

@c42f
Copy link
Owner

@c42f c42f commented Jul 21, 2025

These have been removed upstream on the main branch and replaced with a small number of new Kinds.

@mlechu I cherry picked this change from one of your other branches and separated them out from other things - you're set as the commit author :-)

Am slowly trying to untangle the mess of PRs we've gotten into with me being away 😅

@mlechu
Copy link
Collaborator

mlechu commented Jul 21, 2025

Any reason to apply this change first? My intent was to try and get #10 merged first, then git-wrangle other changes into more polished/manageable PRs.

@c42f
Copy link
Owner Author

c42f commented Jul 21, 2025

Not really necessary, but it makes #10 work with the latest JuliaSyntax dev branch so I thought I could get it merged as a small step to sorting out the mess of branches 😅

mlechu and others added 3 commits August 5, 2025 10:42
These have been removed upstream on the main branch and replaced with a
small number of new `Kind`s.
One test here depends on GreenNode printing which prints the raw flags.
An update to JuliaSyntax will fix that soon.
These won't work with the new `CodeInfo`, so it's pointless to run our
tests on them, for now. At some point it might make sense to make the
non-eval related parts of JuliaLowering work on older versions for use
by tooling packages, but it's unclear this is practical.
@c42f c42f force-pushed the caf/juliasyntax-dev-fixes branch from 63aa9b2 to 3514388 Compare August 5, 2025 02:04
@c42f c42f merged commit 65d6523 into main Aug 5, 2025
1 check failed
@c42f c42f deleted the caf/juliasyntax-dev-fixes branch August 5, 2025 11:04
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.

3 participants