bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity
rust/src/test/rustdoc/intra-link-prim-methods-external-core.rs

19 lines
574 B
Rust
Raw Normal View History

Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
// aux-build:my-core.rs
build extern docs as well
2020-07-06 19:46:53 -07:00
// build-aux-docs
Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
// ignore-cross-compile
Avoid running test on Windows platforms There don't seem to be any other compiletests that are 1) building a standalone "no_core" create and then 2) trying to link against it. There seems to be a platform-specific limitation in doing so: ``` 2020-07-08T16:07:42.9419409Z = note: Creating library D:\a\rust\rust\build\i686-pc-windows-msvc\test\rustdoc\intra-link-prim-methods-external-core\auxiliary\my_core.dll.lib and object D:\a\rust\rust\build\i686-pc-windows-msvc\test\rustdoc\intra-link-prim-methods-external-core\auxiliary\my_core.dll.exp 2020-07-08T16:07:42.9419810Z LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup@12 2020-07-08T16:07:42.9420032Z D:\a\rust\rust\build\i686-pc-windows-msvc\test\rustdoc\intra-link-prim-methods-external-core\auxiliary\my_core.dll : fatal error LNK1120: 1 unresolved externals ``` Possibly this could be resolved by adding a `__DllMainCRTStartup` or `__DllMainCRTStartup@12` symbol in an architecture- and platform-specific way.
2020-07-08 09:48:15 -07:00
// ignore-windows
ignore-tidy-linelength for @has assertions
2020-07-07 10:39:10 -07:00
// ignore-tidy-linelength
Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
intra_doc_resolution_failures -> broken_intra_doc_links
2020-07-30 10:38:55 -07:00
#![deny(broken_intra_doc_links)]
Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
#![feature(no_core, lang_items)]
#![no_core]
Apply #![crate_type = "rlib"] directly to the linker
2020-07-08 08:20:43 -07:00
#![crate_type = "rlib"]
Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
Assert current behavior for links For the two of these tests that have a local `char` to link to, this behavior isn't what's expected, but is what's happening presently.
2020-07-07 10:23:29 -07:00
// @has intra_link_prim_methods_external_core/index.html
// @has - '//*[@id="main"]//a[@href="https://doc.rust-lang.org/nightly/std/primitive.char.html"]' 'char'
// @has - '//*[@id="main"]//a[@href="https://doc.rust-lang.org/nightly/std/primitive.char.html#method.len_utf8"]' 'char::len_utf8'
Two new rustdoc tests for intra links They both produce less-than-desirable output (links going to docs.rust-lang.org), but I haven't figured out yet how to assert about them properly.
2020-07-06 19:35:07 -07:00
//! A [`char`] and its [`char::len_utf8`].
extern crate my_core;
Copy permalink