As i see things...
- From a language specific level (*higher abstraction*) is means *undefined, is the absence of a value. Something whose value is nil/null/undefined is not defined.* - *On a lower level of abstraction it may be tweeking a little bit for having an application/business depedant meaning. **See this example. <https://play.golang.org/p/_ryDhx15LRK> * - The trick is to implement the "Stringer" interace so the fmt.Print* checking if the receiver argument is nil or not. Do note that nil may have sense in more concrete level of abstraction, that is not a new concept, it was already introduced with the null pattern, and here i see it as well (with another custome the principles behind are the same El domingo, 20 de enero de 2019, 20:00:24 (UTC-3), 伊藤和也 escribió: > > I know "nil" is zero values for slices, maps, interfaces, etc but I don't > know what "nil" implays. Does nil implay the absence of value or a variable > has't been initialized yet or something else? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
