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

Jump to bottom

String* may also appear outside of metadata #2276

Closed
borkdude opened this issue Feb 12, 2024 · 2 comments
Closed

String* may also appear outside of metadata #2276

borkdude opened this issue Feb 12, 2024 · 2 comments
Projects
clj-kondo

Comments

@borkdude
Copy link
Member

So clj-kondo --lint - <<< 'String*' should not report an error
@borkdude borkdude added this to Needs triage in clj-kondo via automation Feb 12, 2024
@borkdude borkdude moved this from Needs triage to High priority (next release) in clj-kondo Feb 12, 2024
@borkdude borkdude moved this from High priority (next release) to In progress in clj-kondo Feb 19, 2024
borkdude added a commit that referenced this issue Feb 19, 2024
@borkdude
Fix #2276: new class array notation may occur outside metadata
9313151
clj-kondo automation moved this from In progress to Done Feb 19, 2024
@puredanger
Copy link
Contributor

puredanger commented Mar 14, 2024 •
edited
Loading

fyi, this notation is going to change in next alpha to String::1, watch CLJ-2833. But String* could actually be a valid class name (and deftype can make such a thing), so it should be potentially valid regardless.

@borkdude
Copy link
Member Author

Noted, I'll open a new issue.

@borkdude borkdude mentioned this issue Mar 14, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
clj-kondo
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@puredanger @borkdude