Andrew Baxter

Well, an API would be good either way - relying on internal function names is asking for churn so this PR at the very least would indicate that this is...

Yes, maybe I should have said it would be necessary either way (re-exporting or not).

Actually it would be nice if rather than specifying a prefix like `"/assets"` it could be taken from the route suffix like ``` .at("/assets/*tree", get(EmbeddedFilesEndpoint::::new())) ``` (taking the `*tree` part...

Ah, I see! You're right, I didn't think of that but it seems obvious in retrospect. Thank you!

Firstly, thank you for looking into this! That doesn't make a lot of sense to me, the documentation clearly states > All module imports with non-relative names are assumed to...

It's not clear to me how `paths` would resolve this or how it could be used. My reading from the documentation is that it's a way to override the lookup...

Are the Releases the recommended place to get this? I guess there's no stable release yet, so the Alpha would be the recommended release? I came here from another build...

Excuse me, it looks like `TlsAcceptor` + _is_ provided by this library, but it looks fairly different. I'm still trying to connect things together. Is this functionally the same `TlsAcceptor`...

This is bad because if you try to rename the impl method instead, it tells you to rename the interface method (which breaks everything). This doesn't seem like an exact...

Sorry, just encountered it with concurrent writes too (21921792 bytes in)