Dumping a whole bunch of state into a `Context` struct is an code smell. If you can't think of a better name than context, then it is probably a poor abstraction.
-
-
We do it in tikv too!
How are you planning to resolve it? -
Currently `tide::Context` holds all request data, is generic over global State, and can be extended using ext traits: https://docs.rs/tide/0.2.0/tide/struct.Context.html … The endpoint signature is: async fn (ctx: Context<State>) -> tide::EndpointResult {}
- 5 more replies
New conversation -
-
-
(realize it could be about many things, but like, figured there's a non-zero chance this might have irked you about Tide also haha)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Haha, I am not. It is a pretty pervasive (anti-)pattern in the Rust ecosystem
-
c'mon don't you love 'gcx?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.