Tooltips / IntelliSense: Don't resolve type aliases (aka "semantic sugar") set explicitly
We have defined a bunch of "semantic sugar" type aliases like:  **Status quo (bad):** VS Code is resolving these along the alias chain in tooltips and IntelliSense suggestions (which kinda makes non-sense of the type alias in the first place) (c.f. hovered tooltip over `this.url` at bottom) **Better:** Let VS Code show `UrlString` as type here instead of `string` to aid developers with semantic sugar as of what type of string to expect. **Alternative:** Show both, i.e. `BufferingWebSocket.url: UrlString (= string)`.
Posted by Sgt-Nukem on Jun 17, 2019, 4:37 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Tooltips / IntelliSense: Don't resolve type aliases (aka "semantic sugar") set explicitly
We have defined a bunch of "semantic sugar" type aliases like:  **Status quo (bad):** VS Code is resolving these along the alias chain in tooltips and IntelliSense suggestions (which kinda makes non-sense of the type alias in the first place) (c.f. hovered tooltip over `this.url` at bottom) **Better:** Let VS Code show `UrlString` as type here instead of `string` to aid developers with semantic sugar as of what type of string to expect. **Alternative:** Show both, i.e. `BufferingWebSocket.url: UrlString (= string)`.
Comments (0)
No comments yet. Start the discussion.