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

Jump to bottom

Null-safety of generics, varargs and array elements #878

Open
sdeleuze opened this issue Sep 22, 2017 · 4 comments
Open

Null-safety of generics, varargs and array elements #878

sdeleuze opened this issue Sep 22, 2017 · 4 comments
Assignees
@sdeleuze
Labels
status/on-hold This was set aside or cannot be worked on yet

Comments

@sdeleuze
Copy link
Contributor

See Kotlin/KEEP#79.
@sdeleuze sdeleuze added this to the 3.2.0.RELEASE milestone Sep 22, 2017
@sdeleuze sdeleuze self-assigned this Sep 22, 2017
@simonbasle simonbasle modified the milestones: 3.2.0.RELEASE, [backlog] Mar 2, 2018
@sdeleuze
Copy link
Contributor Author

We are discussing publishing a new null-safety library with JetBrains, that could be a replacement for JSR 305 and provide a solution for generics, varargs and array elements.

Any thoughts about the proposal and my remarks on the PR?

@simonbasle simonbasle removed this from the Backburner milestone Nov 6, 2020
@simonbasle simonbasle added the status/declined We feel we shouldn't currently apply this change/suggestion label Nov 6, 2020
@simonbasle
Copy link
Member

there has been no activity around this in a while

@sdeleuze
Copy link
Contributor Author

sdeleuze commented Nov 6, 2020

In fact there has been quite a lot of activity on other channels, I was about to reach you about that. I am part of the https://github.com/jspecify/jspecify/ project which intent to provide better null safety annotations than JSR one with generics support. We are coming close to a point where we could test that on Reactor (with checks possible in the build and in Idea). Could you update the status accordingly?

@simonbasle simonbasle added status/on-hold This was set aside or cannot be worked on yet and removed status/declined We feel we shouldn't currently apply this change/suggestion labels Nov 6, 2020
@simonbasle
Copy link
Member

got it, waiting to hear more from you then 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdeleuze sdeleuze

Labels
status/on-hold This was set aside or cannot be worked on yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sdeleuze @simonbasle