|
You are here |
golangbot.com | ||
| | | | |
blog.bencope.land
|
|
| | | | | A composed function can be thought of as being more generalized than a pipeline, as a pipeline needs a value to start with while a composed function receives an argrument directly. let clickHandler (value: string) = value |> parse |> sanitize |> serialize |> sendPayload The function above takes an argument, then passes that argument | |
| | | | |
antonz.org
|
|
| | | | | Computing the smallest/largest value and clearing containers. | |
| | | | |
www.alexedwards.net
|
|
| | | | | ||
| | | | |
jbrandhorst.com
|
|
| | | Sometimes when you're writing a server, you've got a function that consumes a lot of memory while running, or some other resource, and you might be worrying that a sudden burst of requests could crash the server, since gRPC by default will just spawn another goroutine to handle any incoming requests, oblivious to the danger. In these situations, it can be useful to implement some custom request throttling. Here I'll show an easy way to accomplish this with the use of a Go channel. | ||