164c2a6cc6
It looks like VS Code does this forcefully. As in, I don't think we can override it. It also seems like a plausibly good idea. But by us doing it too, it makes our completion evaluation framework match real world conditions. (To the extent that "VS Code" and "real world conditions" are the same. Which... they aren't. But it's close, since VS Code is so popular.)
1.1 KiB
1.1 KiB
| 1 | name | file | index | rank |
|---|---|---|---|---|
| 2 | auto-import-skips-current-module | main.py | 0 | 1 |
| 3 | fstring-completions | main.py | 0 | 1 |
| 4 | higher-level-symbols-preferred | main.py | 0 | |
| 5 | higher-level-symbols-preferred | main.py | 1 | 1 |
| 6 | import-deprioritizes-dunder | main.py | 0 | 1 |
| 7 | import-deprioritizes-sunder | main.py | 0 | 1 |
| 8 | import-deprioritizes-type_check_only | main.py | 0 | 1 |
| 9 | import-deprioritizes-type_check_only | main.py | 1 | 1 |
| 10 | import-deprioritizes-type_check_only | main.py | 2 | 1 |
| 11 | import-deprioritizes-type_check_only | main.py | 3 | 2 |
| 12 | import-deprioritizes-type_check_only | main.py | 4 | 3 |
| 13 | import-keyword-completion | main.py | 0 | 1 |
| 14 | internal-typeshed-hidden | main.py | 0 | 5 |
| 15 | none-completion | main.py | 0 | 2 |
| 16 | numpy-array | main.py | 0 | |
| 17 | numpy-array | main.py | 1 | 1 |
| 18 | object-attr-instance-methods | main.py | 0 | 1 |
| 19 | object-attr-instance-methods | main.py | 1 | 1 |
| 20 | pass-keyword-completion | main.py | 0 | 1 |
| 21 | raise-uses-base-exception | main.py | 0 | 2 |
| 22 | scope-existing-over-new-import | main.py | 0 | 1 |
| 23 | scope-prioritize-closer | main.py | 0 | 2 |
| 24 | scope-simple-long-identifier | main.py | 0 | 1 |
| 25 | tstring-completions | main.py | 0 | 1 |
| 26 | ty-extensions-lower-stdlib | main.py | 0 | 8 |
| 27 | type-var-typing-over-ast | main.py | 0 | 3 |
| 28 | type-var-typing-over-ast | main.py | 1 | 279 |