rust/tests/rustdoc-ui/doctest/relative-path-include-bytes-132203.edition2015.stdout, branch stable https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=stable 2025-07-24T09:06:28+00:00 Update rustdoc ui tests 2025-07-24T09:06:28+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-07-22T14:00:25+00:00 urn:sha1:64e3078bbd6b5ac7246735c9ee0a16a091e6f45f Do not suggest using `-Zmacro-backtrace` for builtin macros 2025-03-14T19:50:03+00:00 Esteban Küber esteban@kuber.com.ar 2025-03-11T23:42:36+00:00 urn:sha1:f0b8e13b59a68d63cf7083be5cd6dcca3abf18ff For macros that are implemented on the compiler, we do *not* mention the `-Zmacro-backtrace` flag. This includes `derive`s and standard macros. Enable relative-path-include-bytes on Windows 2025-02-16T10:40:04+00:00 Chris Denton chris@chrisdenton.dev 2025-02-16T10:28:08+00:00 urn:sha1:95a5ecc995f031478708c6c654a196197e71ba20 Ignore Windows due to its differing path syntax 2024-10-30T19:39:05+00:00 Michael Howell michael@notriddle.com 2024-10-30T06:21:54+00:00 urn:sha1:ac7de1a0d925af4504f9fb100be071e2fd346d13 rustdoc: make doctest span tweak a 2024 edition change 2024-10-27T00:56:38+00:00 Michael Howell michael@notriddle.com 2024-10-27T00:46:22+00:00 urn:sha1:1819b4fa2339fcf416c8f3856f19190cab8c54ff Fixes #132203 This is a compatibility hack, because I think the new behavior is better. When an A `include_str!` B, and B `include_str!` C, the path to C should be resolved relative to B, not A. That's how `include!` itself works, so that's how `include_str!` with should work.