|
You are here |
www.ardanlabs.com | ||
| | | | |
matttproud.com
|
|
| | | | | Pop quiz, hot shot: what is the behavior of func f (as defined below) when it is called from a bare gRPC method or HTTP handler as go f(ctx) using the context.Context provided to the handler?1 1 2 3 4 5 6 7 8 9 10 11 func f(ctx context.Context) { // Flimsily make it improbable for this function to continue while the // handler is serving. time.Sleep(time.Second) select { case <-time. | |
| | | | |
hjr265.me
|
|
| | | | | Signals are standardized messages that an operating system can send your programs. Take Ctrl+C for example. When running a program from the terminal and you hit Ctrl+C, you expect the program to end immediately. How does that work, though? Ctrl+C is a shortcut for the POSIX signal SIGINT. By default, this signal causes your program to be terminated. But this is one of those signals you can handle: You can intercept it and do whatever you please. | |
| | | | |
mariocarrion.com
|
|
| | | | | No language changes but really nice additions. | |
| | | | |
lewisdale.dev
|
|
| | | [AI summary] The author reflects on their experience with the first day of Advent of Code, discussing their approach to solving the problem using Rust and a misinterpretation of the question. | ||