Re-export some useful items #106
Conversation
fibonacci1729
force-pushed
the
reexports
branch
from
e10ff9e to
062085f
Compare
itowlson
left a comment
itowlson
left a comment
There was a problem hiding this comment.
Do you want to update samples that use these as part of this PR, or punt to a follow-up? )I am fine with punting, just flagging the thought.)
|
YES. I knew i immediately forgot something that i had planned to do 😆 |
Signed-off-by: Brian Hardock <[email protected]>
fibonacci1729
force-pushed
the
reexports
branch
from
062085f to
bdcad42
Compare
|
I think I got em' all. |
itowlson
left a comment
itowlson
left a comment
There was a problem hiding this comment.
If it's not all then it's an easy follow-up
|
|
||
| pub use wasip3::{ | ||
| http_compat::{IncomingMessage, Request, Response}, | ||
| wit_bindgen::{self, spawn}, |
There was a problem hiding this comment.
I guess the train has already left the station, but re-exporting wasip3 which itself includes all of wit_bindgen makes backwards compat very difficult. We're tying ourselves to the exact public API of two external crates. Maybe that's unavoidable...
There was a problem hiding this comment.
I think wit-bindgen is effectively "std-like" for async Rust guests. wasip3 is a little different but we have to at least secretly re-export it to make #[http_service] work.
No description provided.