Gaubee

我做的方式也和楼主一样的思路，蛋疼的是当我开始写服务端，这样的蛇身数据在同步的时候数据量非常庞大。感觉很头疼。

我自己个人比较常用的，一个和ReturnType类似的PromiseType: ```ts export type PromiseType = T extends Promise ? R : any; ```

我记得const也是块作用域的吧。TDZ也应该探及会好一点。

用issue搭建博客确实是个不错的想法，至少我也这样做了。 多余的提醒一下可以添加标签…… 打算用Appfog整合issues模块和QQ空间的说说模块， QQ空间好说，jsonp格式。 Github有API。 最好是能用QQ账号或者Github账号登陆评论 唯一哀伤的是Github的API的评论功能用起来略微哀伤，Issues也不能按数量获取（只能用后台缓存机制了） 楼主有什么好的想法？关于把Issues模块整合到第三方页面？

If install a transfer handler on the main thread but not the worker, then the worker could not get type-safe object, I still need deserialize in the worker, right?

Or let's focus on the example of WebRTC-WebWorker. First, I use diffrent transfrom code, ```ts /// Master Comlink.transformHanders.set('RTCPeerConnnection',{ canHandle: (obj)=>obj instanceof RTCPeerConnnection, serialize: _serializeRTCPeerConnnection, deserialize: noop, }) ``` ```ts ///...

But event if I implement **Class Binding Serialize** I think people still need **canHandle + serializeOnly** of some special use case. bacause `canHandle` is more powerful.

If you think the code of `TransferHandlerMap` is bloated, we can use redesign the api which is base on typescript, and generate a small amount of JS code. but maybe...

@ChALkeR Very good advice!

@ChALkeR Now I try to work on optimize `$updateImplicit`. The `$updateImplicit` function will be multiple calls in one frame. But I think it should only be called once in a...