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
More importantly, the inlay hint for the a constant, if any, is expected to display [2]SomeType rather than [2](unknown type), as the type is directly available from the RHS of the = sign. Same holds for the inlay hint for v.
Apparently, the whole issue can become obsolete if #1526 is implemented, reporting just in case.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Zig Version
0.12.0
Zig Language Server Version
0.12.0
Client / Code Editor / Extensions
VS Code 1.86.1 (Windows), extension: Zig Language v0.5.7
Steps to Reproduce and Observed Behavior
Enter the following code in the editor:
Observed inlay hints (underscores are used to mark the inlay hints in the code):
Expected Behavior
v
anda
constants are inconsistent to each other. Expected either both inlay hints be present or both be absent (preferably absent, as suggested in Don't show inlay if variable was initialized with a type already #1526).a
constant, if any, is expected to display[2]SomeType
rather than[2](unknown type)
, as the type is directly available from the RHS of the=
sign. Same holds for the inlay hint forv
.Apparently, the whole issue can become obsolete if #1526 is implemented, reporting just in case.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: