Large objects deadlock autocompletion #9

Activity

1. antsmartian commented on Jul 18, 2018

   

   antsmartian

   on Jul 18, 2018

   Last edited by antsmartian

   Contributor

   More actions

   Ok this is interesting. I'm not sure, why we do call onAutocomplete when user types in .? Also, the same code snippet works perfectly fine in normal repl along with proper tab completion. A quick question here can't we simply use Object.getOwnPropertyNames() to get the list of method names here rather than using Runtime.getProperties are there any advantages here?
2. devsnek commented on Aug 21, 2018

   

   devsnek

   on Aug 21, 2018

   Member

   More actions

   I'm going to try and add a timeout to Runtime.getProperties

   👍React with 👍1Reacted by antsmartian
3. cactyx commented on Aug 16, 2019

   

   cactyx

   on Aug 16, 2019

   Last edited by cactyx

   More actions

   I'm not too experienced with child processes in NodeJS (child_process module), but would moving autocompletion / eager evaluation to a killable fork make sense?
   The result would then be shown asynchronously.

   When the input is submitted or is changed to something syntactically different (if there's efficient ways to check this, something like removing a semicolon at the very end shouldn't re-trigger it), the fork could be killed off and the new thing would be evaluated.

   Example from the Chrome devtools (although they don't kill it if it doesn't complete quickly enough but instead it clogs the main process):
   

   👍React with 👍1Reacted by __