dependabot-preview[bot] on cargo
dependabot-preview[bot] on cargo
Update tokio-tungstenite requir… (compare)
dependabot-preview[bot] on cargo
_without_pipelines
BorrowBags
exist to make a collection of disparate things share a (longer) lifetime, right?
construct
going on in there, and Pilelines
-> PipelineInstances
and NewMiddlewareChain
-> MiddlewareChain
but that confuses the issue)
call
ed during a request, we instantiate what amounts to a list of lists, and then do a depth first walk with the (state, request) pair, and then walk back with the result.
PipelineHandleChain
s compose with MiddlewareChain
s since both convert a cadr-style list into function composition, with (state,request) running down the side.
unsafe
async
just Pin<Future<T>>
?
impl Future
async fn foo() -> Result
translates to fn foo() -> impl Future<Output = Result>
with no boxing involved, and the concrete type being inferred by the compiler (and which is also some autogenerated private type)
bind_server
(source) to see (a) if it would be enough, (b) how it's dont internally.
Cargo.lock
, should not in fix / expose feature from hyper
? I have no rust
skill but hyper
is in 0.14
so we need to fix version in Cargo.toml
gotham::hyper
and don't depend on your own version of hyper
gotham_middleware_diesel
table, but I guess I'd expect someone to have done so already. :-) (In the absence of a pre-existing one the MemoryBackend
will realistically be fine for my one-off application for a child's distributed birthday party)