You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To help the JSpecify community I try to run all the various null analysis tools out there on my opensource projects core modules (core modules are easier because they usually do not have dependencies).
So far I am testing/using in my github CI pipelines:
Checkerframework
Eclipse
NullAway
I plan on adding the reference checker and my plan was just to fork the repository and publish to my own SNAPSHOT repository.
Is this a bad idea?
Would this cause confusion?
Is there already a SNAPSHOT repo I'm unaware of?
Perhaps this question was better for the Google Groups (so feel free to close)?
The text was updated successfully, but these errors were encountered:
#218 updates some versions and fixes a problem, please try with that change or once that PR is merged.
I think it would be good to make an official, easy-to-use, but unsupported, release. Hopefully soon.
The reference checker builds on the EISOP fork of the Checker Framework. It would probably be easier to just use one version of the CF. EISOP contains a few JSpecify-specific changes and also some improvements to the Nullness Checker, most importantly cleanly separating nullness from initialization.
It should be easy to switch over by changing the dependencies, e.g. see this build file.
To help the JSpecify community I try to run all the various null analysis tools out there on my opensource projects core modules (core modules are easier because they usually do not have dependencies).
So far I am testing/using in my github CI pipelines:
I plan on adding the reference checker and my plan was just to fork the repository and publish to my own SNAPSHOT repository.
Is this a bad idea?
Would this cause confusion?
Is there already a SNAPSHOT repo I'm unaware of?
Perhaps this question was better for the Google Groups (so feel free to close)?
The text was updated successfully, but these errors were encountered: