<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>内部编译器错误 on Tony Bai</title><link>https://tonybai.com/tags/%E5%86%85%E9%83%A8%E7%BC%96%E8%AF%91%E5%99%A8%E9%94%99%E8%AF%AF/</link><description>Recent content in 内部编译器错误 on Tony Bai</description><generator>Hugo</generator><language>zh-cn</language><copyright>2004-2026 Tony Bai. 版权所有.</copyright><lastBuildDate>Sun, 30 Nov 2025 00:00:00 +0800</lastBuildDate><atom:link href="https://tonybai.com/tags/%E5%86%85%E9%83%A8%E7%BC%96%E8%AF%91%E5%99%A8%E9%94%99%E8%AF%AF/index.xml" rel="self" type="application/rss+xml"/><item><title>Go 编译器崩溃背后：一个 append 函数引发的语言规范修正案</title><link>https://tonybai.com/2025/11/30/ice-assertion-failed-with-append/</link><pubDate>Sun, 30 Nov 2025 00:00:00 +0800</pubDate><guid>https://tonybai.com/2025/11/30/ice-assertion-failed-with-append/</guid><description>本文永久链接 – https://tonybai.com/2025/11/30/ice-assertion-failed-with-append 大家好，我是Tony Bai。 在软件开发中，我们有时会遇到一些“显而易见”的错误。对于 Go 开发者而言，append 内建函数的第一个参数必须是切片，似乎就是这样一个“常识”。然而，当一个本应产生清晰编译错误的“常识性”错误，却导致了 Go 1.25...</description></item></channel></rss>