You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2020. It is now read-only.
Not sure this is solvable without leveraging more of cargo. The approach of compiling using rustc will lead us down a path of basically recreating cargo. Already looking at this I ran into issues where a crate like hyper has two different versions of the slab crate.
When generating documentation tests, the following stages will happen:
- tests will be gathered from the docs as a list of strings
- tests will be saved to target/doc/tests as individual files
- tests will be compiled into a single binary called "rustdoc-test"
- tests will be run by executing the "rustdoc-test" binary
Doc tests are now actual tests. This allows us to take advantage of the
existing test infrastructure supplied by rustc.
Fixessteveklabnik#32, steveklabnik#54, steveklabnik#219
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Download hyper and checkout tag
v0.11.9
. Run the tests:The tests fail because the test program does not extern the base64 crate.
The text was updated successfully, but these errors were encountered: