WÁNG Xuěruì

> 这个项目是可以实现 企微信息聚合的功能？看起来跟wechaty好像 似乎不是吧，那个项目似乎专注在 chatbot 这个领域上（而且神奇的是 chatbot 明明是疼讯会重拳出击整治的使用姿势，居然它的官网上还列出了疼讯是 sponsor……），而本项目就是把 API 都包一层的无聊的 SDK 而已 此外，这个 issue 是用来征集 co-maintainer 的，阁下有意帮忙？

> [微信客服-获取客户基础信息](https://developer.work.weixin.qq.com/document/path/95159) > > 我也可以自己开发，协同维护的 欢迎 PR!

Ping

@xry111 @ChenghuaXu @scylaac @FreeFlyingSheep @yetist 大家怎么看？

For the record: this is causing significant pain for the LLD port, where relocation semantics (the `RelExpr` enum) has to be determined early and ideally without depending on other relocs/input...

I've just removed all `AnyStr_co` occurrences and fixed the rest of signature mistakes pointed out in the review comments.

It seems mypy cannot handle the re-import of `Repository` with different types if the star-imports have to be preserved in the stubs: ``` stubs/pygit2/pygit2/__init__.pyi:24: error: Incompatible import of "Repository" (imported...

It seems simply ignoring the type check error on the `Repository` re-import doesn't work. When I was working on a project with the content of this PR integrated into its...

> No recent failures reported by `watchflakes`. @golang/loong64 — was this fixed on the builder, or by some mitigation in the compiler or linker, or is there more to do...

My two cents: > Who will maintain the loongarch64-unknown-linux-gnu? Aside from the Loongson teams, there is [an active community around LoongArch](https://bbs.loongarch.org/) (also [Telegram user group](https://t.me/loongson_users)) with multiple porters and power...