Without experience with compiler behavior, the agent couldn't have predicted which 'optimizations' the compiler would already handle.
这一观察揭示了AI代理在编译优化方面的局限性：代理无法准确预测编译器已经自动处理的优化。这表明AI代理需要更深入理解编译器行为和现代编译技术，以避免徒劳的优化尝试。这一发现对AI辅助编程系统的发展具有重要启示，强调了领域知识整合的重要性。
If you manage to make Svelte aware of what needs to be tracked, chances are that the resulting code will be more performant than if you roll your own with events or whatever. In part because it will use Svelte's runtime code that is already present in your app, in part because Svelte produces seriously optimized change tracking code, that would be hard to hand code all while keeping it human friendly. And in part because your change tracking targets will be more narrow.