2 ms·
In no particular order: No sane story for request contexts. I got tired of waiting for net/http support for x/net/context. Coercing Go structs into JSON and v
by jrobn 11y ago
In no particular order:
No sane story for request contexts. I got tired of waiting for net/http support for x/net/context.
Coercing Go structs into JSON and vice versus was just annoying enough. I felt like I was paying the price (being more explicit) for static typing without a lot of the benefits of other static typed languages.
and this: //go:generate stringer -type=Pill [https://blog.golang.org/generate https://blog.golang.org/generate]
- ngrilly 11y ago> No sane story for request contexts. I got tired of waiting for net/http support for x/net/context. This is moving forward. A package context would probably be added to the standard library and integrated with net/http.Request: https://github.com/golang/go/issues/14660 https://github.com/golang/go/issues/14660 How is this issue solved in Erlang/Elixir? > Coercing Go structs into JSON and vice versus was just annoying enough. I had the same feeling when I started using Go (coming from Python/JS, and Java/C++ a long time ago). But then I realised that I have to validate my inputs anyway, even in Python, JS or Erlang. Defining a struct and unmarshal to the struct gives me that for free in Go. How do you solve that in Erlang/Elixir?