3 ms·
It's too dangerous to execute the code to provide completion support. IDE support has to rely on static analysis.
by djur 3y ago
It's too dangerous to execute the code to provide completion support. IDE support has to rely on static analysis.
- heads 3y agoI suppose you could run the unit test suite?
- dpassens 3y agoNo, you couldn't. If running the code is too dangerous, then so is running the unit test suite. You'd have to prove that it doesn't do anything observable, like accidentally deleting your home directory, or, if the code is actively malicious, uploading your SSH key somewhere. And if you can do that, you probably also have enough information to provide good completion without running the code.
- vidarh 3y agoYou can get quite far by symbolic evaluation of a fairly small subset of Ruby - the most common patterns used use a fairly small number of methods. Frankly I think not going further is a good thing in that it'll discourage people from going unnecessarily far with the dynamic features.