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.

Sign up for GitHub

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

fixed out-of-date message on typechecker and removed hard version number references to rascal project #522

Merged
merged 2 commits into from
Feb 14, 2025
Merged

fixed out-of-date message on typechecker and removed hard version number references to rascal project #522

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
09e3084
fixed out-of-date message on typechecker and removed hard version num…
jurgenvinju Nov 18, 2024
a0174bc
Added a version clarification to the message
DavyLandman Feb 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions rascal-vscode-extension/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,11 @@ This extension is stabilizing, some stuff is still a bit slow, but people are us

**This extension works best with Java 11; but running it on Java 17 reportedly works as well**

The Rascal type-checker has a known issue that makes **new binary library code backward incompatible** after every release, always. This means that you
should update your dependency on the `rascal` project to at least 0.33.7 and maximally 0.33.8 in your own projects to avoid spurious error messages. For the
same reason you have to set your use of the `rascal-maven-plugin` to 0.22.1. Until
we release a fix for the type-checker, all rascal projects and library packages on http://www.rascal-mpl.org are released synchronously. Consequently, after you
installed an update, it is immediately necessary to bump your dependencies on `rascal` and `rascal-maven-plugin`.
The Rascal type-checker now has a new binary backward compatibility feature, such that `.tpl` files remain usable
in many more situations. Also the type-checker detects and reports possible `.tpl` file incompatibility from now on.
Typically, the previous versions of .tpl files are not compatible with the new ones, so to avoid spurious errors
you _must remove all pre-existing `.tpl` files_ after upgrading. Use `mvn clean`, for example. Or remove your
`target` or `bin` folder in every Rascal project. This backwards compatiblitiy functionality is available since rascal 0.40.17, typepal 0.14.8, rascal-maven-plugin 0.28.9, and Rascal VS Code 0.12.0.

For other things we are working on have a look here:
* https://github.com/usethesource/rascal-language-servers/issues ; on the current extension
Expand Down
Loading