-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Swift: Support new Swift 6.1 AST elements #19420
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
Conversation
5dc41fe
to
8ffe78c
Compare
swift/ql/lib/codeql/swift/elements/type/internal/BuiltinFixedArrayTypeImpl.qll
Fixed
Show fixed
Hide fixed
ebaebd1
to
b8e7f5d
Compare
b8e7f5d
to
95ac458
Compare
| type_value_exprs.swift:4:13:4:13 | TypeValueExpr | hasType: | yes | getTypeRepr: | type_value_exprs.swift:4:13:4:13 | (no string representation) | | ||
| type_value_exprs.swift:5:13:5:13 | TypeValueExpr | hasType: | yes | getTypeRepr: | type_value_exprs.swift:5:13:5:13 | (no string representation) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why I'm seeing (no string representation)
here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, that is odd, I thought there was a default implementation in place (using the primary class). We can look at it in a follow up I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!
I think the "no string representation" might be worth a bit of investigation, but I don't think it's blocking for this PR 👍
Great. In that case I merge this PR once DCA looks ok, and I'll create a follow-up issue for the "no string representation". |
No description provided.