ade7ecf909
This is shorter, avoids potential conflicts with a crate named `implementors`[^1], and will be less confusing when JS include files are added for type aliases. [^1]: AFAIK, this couldn't actually cause any problems right now, but it's simpler just to make it impossible than relying on never having a file named `trait.Foo.js` in the crate data area.
21 lines
630 B
Rust
21 lines
630 B
Rust
// aux-build:rustdoc-impl-parts-crosscrate.rs
|
|
// ignore-cross-compile
|
|
|
|
#![feature(negative_impls)]
|
|
|
|
extern crate rustdoc_impl_parts_crosscrate;
|
|
|
|
pub struct Bar<T> { t: T }
|
|
|
|
// The output file is html embedded in javascript, so the html tags
|
|
// aren't stripped by the processing script and we can't check for the
|
|
// full impl string. Instead, just make sure something from each part
|
|
// is mentioned.
|
|
|
|
// @hasraw trait.impl/rustdoc_impl_parts_crosscrate/trait.AnAutoTrait.js Bar
|
|
// @hasraw - Send
|
|
// @hasraw - !AnAutoTrait
|
|
// @hasraw - Copy
|
|
impl<T: Send> !rustdoc_impl_parts_crosscrate::AnAutoTrait for Bar<T>
|
|
where T: Copy {}
|