Thanks! In my view, whenever you are dealing with data, this (null situation) is inevitable, which makes it so useful and so fundamental that it should be considered as part of the future Go. Otherwise, you will see different people doing different things, just like different people using different string implementation in C, and we end up with many C string libraries and implementations that are incompatible with each other.
Go has done a great job eliminating such problems and should continue doing so. On Sun, Aug 20, 2017 at 1:13 PM, Tamás Gulácsi <tgulacs...@gmail.com> wrote: > Tgis is what sql.NullInt64 does, or github.com/guregu/null . > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/EGwyXVCXrY8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
