# Docs.rs don't build docs for procedural macro

**URL:** <https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068>\
**Category:** tools and infrastructure\
**Created:** [October 8, 2019, 7:37am UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068 "2019-10-08T07:37:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![la10736](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/la10736/32/3435_2.png) [@la10736](https://internals.rust-lang.org/u/la10736)\
**Post date:** [October 8, 2019, 7:37am UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068/1 "2019-10-08T07:37:03Z")

</div>

Hi, after release last version of my crate (a procedural macro library) I saw that the documentation on Docs.rs is missing. On Docs.rs there is just a _rstest-0.4.1 is not a library._ message with _Crate_ and _Source_ tabs but no Docs.

I've dig a little and I noted that every procedural macro crate released in the last days have the same behavior.

Now I don't know if it is related to the lest changes on Docs.rs or just a bug, but I would like to know if it is what I should expect for the next releases. I filled a bug on Docs.rs [https://github.com/rust-lang/docs.rs/issues/422](https://github.com/rust-lang/docs.rs/issues/422) but I haven't received any feedback ☹

Somebody know what's happening?

---

<div class="post-metadata">

**Author:** ![kornel](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/kornel/32/2711_2.png) [@kornel](https://internals.rust-lang.org/u/kornel)\
**Post date:** [October 8, 2019, 1:41pm UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068/2 "2019-10-08T13:41:31Z")

</div>

Recently docs.rs has cut off network access and made everything outside `target/` read-only. Do you accidentally rely on any of these?

> **[Upcoming docs.rs changes | Rust Blog](https://blog.rust-lang.org/2019/09/18/upcoming-docsrs-changes.html)**
>
> Empowering everyone to build reliable and efficient software.

---

<div class="post-metadata">

**Author:** ![la10736](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/la10736/32/3435_2.png) [@la10736](https://internals.rust-lang.org/u/la10736)\
**Post date:** [October 8, 2019, 1:56pm UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068/3 "2019-10-08T13:56:38Z")

</div>

No ... I guess. I'm creating and deleting files just in tests but never at compile time.

The crate use a simple `build.rs` script to catch nightly channel and a very small set of dependencies.

dependencies:

```rust
cfg-if ^0.1
itertools ^0.8
proc-macro2 ^1.0
quote ^1.0
rustc_version ^0.2
syn ^1.0

```

dev-dependencies

```rust
lazy_static ^1.1
pretty_assertions ^0.6
temp_testdir ^0.2
toml_edit ^0.1
unindent ^0.1.4

```

Have you see any procedural macro crate where docs is rendered in the last 4 days? In any case, when a limitation is hit should be present a message that explain this case and not just _is not a library_... Isn't it?

Thanks

---

<div class="post-metadata">

**Author:** ![la10736](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/la10736/32/3435_2.png) [@la10736](https://internals.rust-lang.org/u/la10736)\
**Post date:** [October 8, 2019, 4:58pm UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068/4 "2019-10-08T16:58:43Z")

</div>

Ok... It's a bug 😄

> <https://github.com/rust-lang/docs.rs/issues/422>

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\
**Post date:** [January 6, 2020, 4:58pm UTC](https://internals.rust-lang.org/t/docs-rs-dont-build-docs-for-procedural-macro/11068/5 "2020-01-06T16:58:44Z")

</div>

Closed on January 6, 2020, 4:58pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.