Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bumped to latest rascal release #2

Merged
merged 4 commits into from
Oct 17, 2024
Merged

Conversation

DavyLandman
Copy link
Member

Note, this depends on a release of usethesource/salix-core before this can be completed. This means it needs usethesource/salix-core#8 to get merged, and after then a new maven release.

@DavyLandman DavyLandman force-pushed the chore/update-to-latest-rascal branch from bda82e7 to e1a7d77 Compare June 14, 2024 12:35
@DavyLandman DavyLandman force-pushed the chore/update-to-latest-rascal branch from e1a7d77 to 2a9b0b4 Compare June 14, 2024 12:36
@jurgenvinju
Copy link
Member

This is a good and complex test for binary dependency with the latest Compiler

@DavyLandman
Copy link
Member Author

DavyLandman commented Aug 30, 2024

So, yes, it breaks in VS Code (still working on an bug report) the dependency if both projects are open, but it works nicely in rascal-maven-plugin. and it revealed one new error in the typechecker: usethesource/rascal#2026

@DavyLandman
Copy link
Member Author

Okay, the VS Code bug is already known: usethesource/rascal-language-servers#243

@DavyLandman DavyLandman merged commit 7dcc549 into main Oct 17, 2024
1 check passed
@DavyLandman DavyLandman deleted the chore/update-to-latest-rascal branch October 17, 2024 13:11
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