Heejae Chang

also, we might let users to use different type checker such as this - https://github.com/microsoft/vscode-mypy with pylance LS. but it also means some type tooltip pylance shows might not agree...

> Looks like you added this comment [a long time ago](https://github.com/microsoft/pyrx/pull/475/files#diff-21ac918244ac40f42bc0e7910fa838eea9b494c2790f635cd4ff7a1a461e8dfeR89). Do you remember why we filter out aliases? if you enable alias in user file, now you need to...

> https://github.com/microsoft/pyrx/issues/4199 find all reference doesn't consume indices or indexer so, not sure whether 2 would affect each other.

see related issue - https://github.com/microsoft/pylance-release/issues/5231

we probably need something `VS` provide from `vscode`. `VS` provide filtering for `completion` 

Currently, we only perform 'alias deduplication' on third-party packages. For user files, we expect packages to be imported directly, without using aliases. However, we can consider implementing this feature if...

so, our response is correct. should we give it to VS LSP client team? since it looks like it is VS LSP client that filter Context out.

can you share a repro project with us? like github repo with sample code that repro the issue? or at least, give us step by step instructions and file structures...

whether current method override a method or not is cheap, but finding out whether other classes overriding this method is expensive. that's why we are hesitant. but once we do...

looks like our regex for doc string doesn't work properly with Korean. (or any other language except English)