Strahinja Val Markovic 6c53bad58f No more threading in completers! ... The server is multi-threaded and will spawn a new thread for each new request. Thus, the completers need not manage their own threads or even provide async APIs; we _want_ them to block because now were implementing the request-response networking API. The client gets the async API through the network (i.e., it can do something else while the request is pending).		2013-10-07 11:03:28 -07:00
..
all	No more threading in completers!	2013-10-07 11:03:28 -07:00
c	Now more explicit about accessing user options	2013-10-07 11:03:25 -07:00
cpp	No more threading in completers!	2013-10-07 11:03:28 -07:00
cs	No more threading in completers!	2013-10-07 11:03:28 -07:00
general	No more threading in completers!	2013-10-07 11:03:28 -07:00
objc	Now more explicit about accessing user options	2013-10-07 11:03:25 -07:00
objcpp	Now more explicit about accessing user options	2013-10-07 11:03:25 -07:00
python	No more threading in completers!	2013-10-07 11:03:28 -07:00
__init__.py	Moving everything under pytho/ycm	2013-05-19 19:44:42 -07:00
completer_utils_test.py	g:ycm_semantic_triggers now only adds new triggers	2013-06-29 11:53:16 -07:00
completer_utils.py	Decoupling completers from Vim; still WIP & broken	2013-10-07 11:03:25 -07:00
completer.py	No more threading in completers!	2013-10-07 11:03:28 -07:00
general_completer.py	Now more explicit about accessing user options	2013-10-07 11:03:25 -07:00