# fmt Published articles for fmt. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## C++29 -- начало. Встреча ISO C++ в Брно DevFeed: [C++29 -- начало. Встреча ISO C++ в Брно]() Original publisher: [Read original article]() Author: antoshkka (Яндекс) Published: 2026-08-17T07:01:31Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [C++](), [floating-point](), [implementation]() Tags: [c-plus-plus](), [c-plus-plus-29](), [floating-point](), [fmt](), [format](), [implementation](), [iso](), [standard](), [standard-library](), [tagged-pointers](), [thread](), [threads](), [undefined-behavior](), [undefined-behaviour]() ### AI overview A report on the ISO C++ committee meeting in Brno, where work on C++29 began. It describes plans to organize and clarify documented undefined behavior and ill-formed-no-diagnostic-required cases, along with changes involving constexpr floating-point evaluation and other language rules. ### Source excerpt Привет! На связи Антон Полухин из Техплатформы Городских сервисов Яндекса. Недавно в Брно состоялась встреча международного комитета по стандартизации языка программирования C++, в которой я принимал активное участие. В этот раз началась работа над C++29 и как раз о новинках и хочется рассказать. Читать далее ## Golang Interface 内部实现 DevFeed: [Golang Interface 内部实现]() Original publisher: [Read original article]() Author: Joway Published: 2021-01-20T00:00:00Z Content type: tutorial Language: zh Sources: [Random Thoughts]() Topics: [interface]() Tags: [fmt](), [implement](), [interface](), [run](), [tech](), [type]() ### AI overview The article explains how Golang interface values are represented internally and how a non-atomic assignment can leave type information present while the stored pointer is nil. This can make a nil check fail, allow a type conversion to succeed, and cause a panic only when the method is called. ### Source excerpt 最近遇到一个由于 Golang Interface 底层实现，引发的线上 panic 问题，虽然根源在于赋值操作没有保护起来，却意外地发现了关于 interface 的一些有意思的底层细节。 假设我们现在有以下定义： type Interface interface { Run() } type Implement struct { n int } func (i *Implement) Run() { fmt.Printf(i.n) } 对于使用者而言，一个变量无论是 Interface 类型或是 *Implement 类型，差别都不大。 ## Macro View of Map Internals In Go DevFeed: [Macro View of Map Internals In Go]() Original publisher: [Read original article]() Published: 2013-12-31T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Code]() Tags: [ardan-labs](), [blog](), [fmt](), [go](), [go-programming](), [golang](), [hash](), [internals](), [map](), [maps](), [memory](), [padding](), [programming](), [range]() ### AI overview This tutorial explains how Go maps are created and used, why iteration order is not guaranteed, and how maps are organized internally as hash tables with power-of-two bucket counts. It also introduces bucket selection, overflow, and memory padding. ### Source excerpt Introduction There are lots of posts that talk about the internals of slices, but when it comes to maps, we are left in the dark. I was wondering why and then I found the code for maps and it all made sense. https://golang.org/src/runtime/hashmap.go At least for me, this code is complicated. That being said, I think we can create a macro view of how maps are structured and grow. This should explain why they are unordered, efficient and fast. Creating and Using Maps Let's look at how we can use a map literal to create a map and store a few values: ## Functions and Naked Returns In Go DevFeed: [Functions and Naked Returns In Go]() Original publisher: [Read original article]() Published: 2013-10-10T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Error Handling](), [Compiler]() Tags: [ardan-labs](), [blog](), [code](), [error-handling](), [fmt](), [function](), [go](), [go-error-handling](), [go-programming](), [golang](), [programming](), [scope](), [shadowing](), [variable]() ### AI overview This Go tutorial explains returning multiple values, handling errors through returned error values, ignoring a return value with an underscore, naming return arguments, and using naked returns. It also warns about variable shadowing and explains how braces create new scopes. ### Source excerpt In Go values that are returned from functions are passed by value. Go gives you some nice flexibility when it comes to returning values from a function. Here is a simple example of returning two values from a function: package main import ( "fmt" ) func main() { id, err := ReturnId() if err != nil { fmt.Printf("ERROR: %s", err) return } fmt.Printf("Id: %d\n", id) } func ReturnId() (int, error) { id := 10 return id, nil } The function ReturnId returns a value of type integer and of type error. This is something very common that is done in Go. Error handling is performed by returning a value of type error from your functions and the calling function evaluating that value before continuing. If you don't care about the error for some reason after a function call returns, you can do something like this: id, _ := ReturnId() This time I used an underscore to represent the return value for the second return argument, which was the error. This is really nice because I don't need to declare a variable to hold the value being passed in, I can simply ignore it. You also have the option to name your return arguments: func ReturnId() (id int, err error) { id = 10 return id, err } If you name your return arguments you are creating local variables just like with your function parameters. This time when I set the id variable, I remove the colon (:) from the short variable declaration and convert it to an assignment operation. Then in the return I specify the return variables as normal. Naming your return arguments is a nice way to document what you are returning. There is also something else that you can do with your named arguments, or not do: func ReturnId() (id int, err error) { id = 10 return } This is what is called a naked return. I have removed the arguments from the return statement. The Go compiler automatically returns the current values in the return arguments local variables. Though this is really cool you need to watch for shadowing: func ReturnId() (id int, err error)