Explore >> Select a destination
|
You are here 
|
kokada.dev | ||
| | | | |
www.cppstories.com
|
|
| | | | | In my last two posts in the C++17 STL series, I covered how to use std::optional. This wrapper type (also called "vocabulary type") is handy when you'd like to express that something is 'nullable' and might be 'empty'. For example, you can return std::nullopt to indicate that the code generated an error... but it this the best choice? | |
| | | | |
kokada.capivaras.dev
|
|
| | | | | ||
| | | | |
lukesingham.com
|
|
| | | | | These are my summary notes of 'A Tour of Go' - which is meant for people who are familiar with programming to have a quick tour | |
| | | | |
hjr265.me
|
|
| | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | ||
