https://blog.ast.moe/en/tags/go/Recent posts: GorimuchuHugohttps://blog.ast.moe/en/blog/2026-09-30-2/Wed, 30 Sep 2026 22:38:00 +0900https://blog.ast.moe/en/blog/2026-09-30-2/<h2 id="overview">Overview</h2> <p>I created mikoto (<a href="https://github.com/ieee0824/mikoto">source</a>), a tool that checks the length of Go functions and the purity constraints explicitly specified for functions. By annotating a function declaration with <code>//mikoto:pure</code>, it inspects inputs and outputs that use only value types, access to package variables, modifications of referenced objects, pointer indirection, call targets, and so on. The implementation uses Go’s AST and type information, limiting the scope of inspection to function declarations within the same package.</p>https://blog.ast.moe/en/blog/2026-09-28/Mon, 28 Sep 2026 12:42:00 +0900https://blog.ast.moe/en/blog/2026-09-28/<p>In 2018 I wrote an article titled “I Want to Validate Phone Numbers.” It was a brief post introducing the newly started <a href="https://github.com/ieee0824/go-tel-num-parser-jp">go-tel-num-parser-jp</a> project and showing how to use <code>IsTelNumber</code>. (<a href="https://blog.ast.moe/blog/2018-11-08/">source</a>)</p> <p>I made a few more tweaks afterward, but the repository’s updates stopped in 2020. When I revisited it after a long time, I found that the phone number categories were still the same as back then, and there were some issues with the validation method. So, by looking at the currently published number information, I updated the number categories and validation logic (see pull request #4). (<a href="https://github.com/ieee0824/go-tel-num-parser-jp/pull/4">PR #4</a>)</p>