Differentiate methods/functions or fields in autocompletion for R6 class.
See original GitHub issuemlr3 is implemented with R6 class. However, after creating a task, all autocompletes appear to be fields. Some of them actually should be methods, such as data
in the screenshot below.

Can these be differentiated within VSCode?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
14 R6 - Advanced R
By convention, R6 classes have UpperCamelCase names. The second argument, public , supplies a list of methods (functions) and fields (anything else) that ......
Read more >Review VSCodes new Interactive Window for use in this extension ...
@renkun-ken renkun-ken mentioned this issue on Jul 15. Differentiate methods/functions or fields in autocompletion for R6 class. #999.
Read more >14.2 Classes and methods | Advanced R
By convention, R6 classes have UpperCamelCase names. The second argument, public , supplies a list of methods (functions) and fields (anything else) that ......
Read more >Documenting R6 classes and methods within R package in ...
My goal is to get the autocompletion in RStudio for the methods. At the moment, I only get the name of the method...
Read more >Topic 1 CS314 Course Introduction - UT Computer Science
numCols() returns number of columns in the matrix iCells ... or if I ran the algorithm a large number of times with different...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If we have a vscode interactive window suggested in #700 which is built on top of a fully managed background R session, then it seems to be easier to manage these connections and conduct on-demand operations with the R session.
The overhead of getting the information already seems significant. I think it might be use-able if we develop an on-demand mechanism that only access the info of a requested object, which requires two-way communication, as we discussed at #440 and #594.