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
xbt573 opened this issue
Jan 31, 2025
· 3 comments
Labels
bugSomething isn't workingpinnedThis issue or pull request is pinned and won't be marked as stalevscodeThis pull request should be included in the VS Code extension's release notes
For anyone looking into this, the problem is that we currently don't use RBS for default gems. We index them directly from the Ruby installation. That means we can only index Ruby files and we miss definitions made in C.
We can't simply start indexing RBS because that will cause duplicate declarations to be inserted in the index, so we may need to look into dropping our indexing of the Ruby installation and rely on RBS only for default gems.
That would degrade indexing performance because we'd essentially be indexing the same thing twice. Ideally, if we can completely avoid reaching for the Ruby installation, then we can make indexing faster in addition to fixing the missing declarations.
bugSomething isn't workingpinnedThis issue or pull request is pinned and won't be marked as stalevscodeThis pull request should be included in the VS Code extension's release notes
Description
Ruby LSP Information
VS Code Version
1.96.2
Ruby LSP Extension Version
0.8.19
Ruby LSP Server Version
0.23.7
Ruby LSP Add-ons
Ruby Version
3.4.1
Ruby Version Manager
rbenv
Installed Extensions
Click to expand
Ruby LSP Settings
Click to expand
Workspace
User
Reproduction steps
Code snippet or error message
Digest::SHA2.hexdigest
example:Zlib
example:Both
zlib
module andhexdigest
functions are defined inside C files, but have definition in RBS files.The text was updated successfully, but these errors were encountered: