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
[SR-15411] Report cursor info information for literals #57725
Comments
IIUC you are reporting an issue that is specific to Xcode, not SourceKit-LSP. For Xcode-specific issues, could you file a feedback at https://feedbackassistant.apple.com? |
@ahoppen, it's not specific to Xcode. As an example, in VS Code you get the Quick Help pop-up by hovering a variable. |
Ah, OK, I see what you mean now: Both Xcode and SourceKit-LSP should provide QuickHelp/Document Highlight for literals. To make sure the bug report only talks about open source components, I have rephrased it around the underlying |
This seems like it is not being worked on? I would be happy to contribute a patch. |
Adds literals support for the CursorInfo request. Previously CursorInfo just returned error for literals. Implements issue apple#57725
Additional Detail from JIRA
md5: 085af8993d7db2679bf69ce553a24cc0
Issue Description:
In the following test case, SourceKit should provide cursor info for the literal
42
, reporting its type asDouble
. Currently, it doesn’t return any information at all.Original report:
Currently, clicking on a literal while holding the alt key in Xcode won't trigger a Quick Help pop-up. It may be useful for newcomers to be able to get the inferred type of a literal simply by invoking Quick Help.
In the Swift Forums' thread https://forums.swift.org/t/how-to-understand-the-int-double-conversion-in-swift/53063, a new user stumbled upon
Quick Help triggered on the literal
3
at the first line or at the third-to-last line, would showA similar enhancement could be made to operator identifiers too, which would make easier for users to understand which overload has been chosen by the constraint solver.
The text was updated successfully, but these errors were encountered: