I like how Ferd Hebert frames this. When parts of a system evolve at different speeds, they desynchronize. The pieces drift apart silently until an incident forces resynchronization, everyone snapping back to a shared understanding of how things actually work. The review gate is one of the few remaining sync points between “someone changed something” and “production is now different.” Remove it and you don’t make things faster. You make drift invisible until something breaks. And frankly, part of the reason teams feel comfortable generating this much code in the first place is that the review gate exists. Take it away and I doubt anyone would be lobbing changes into production with the same confidence.
then { done = true; state = s; }。新收录的资料对此有专业解读
10 monthly gift articles to share，更多细节参见新收录的资料
The code labelled “Block 2” does not correspond directly to any code in the recursive function; it is pure incidental complexity. When we find ourselves processing a FoldTreeFrame it may be because we are entering it for the first time after a parent call created it, or it may be because we are re-entering it after a child frame’s execution completed. This means that, before we make a recursive call in block 3, we need to check whether that call has already been completed. If so, we run whatever logic should happen after the recursive call. In this case there is no such logic in foldTree so we only need to deal with the mechanical concerns of returning to our parent frame.，这一点在新收录的资料中也有详细论述
如今，这一功能再度被延期。OpenAI发言人近日在接受Axios采访时表示，公司正在“推迟成人模式的上线”，以便优先处理“当前对更多用户来说更重要”的工作，例如继续提升模型的智能水平、性格表现，以及让聊天机器人变得更加“主动”。该发言人同时强调，公司“依然相信应当在原则上把成年人当作成年人看待，但要把整体体验打磨到位，需要更多时间”。