Skip to content

docsrs_dep is not a cfg attribute. #58

@mageowl

Description

@mageowl

variadics_please version

v1.1.0

Relevant system information

This section is optional. Remove it if you know that the problem is not platform dependent.

Rust version you're using:

cargo 1.93.0 (083ac5135 2025-12-15)

Notes:

  • Pay attention to the msrv (minimum supported rust version) of variadics_please.
  • nightly should work, but sometimes there are regressions: please let us know!

Operating system, including version:

NixOS 26.05.20251218.c6245e8

What you did

When using the #[doc(fake_variadic)] feature, cargo emits the warning:

warning: unexpected `cfg` condition name: `docsrs_dep`
  --> golm/src/compiler_modules/syscall.rs:49:1
   |
49 | / all_tuples!(
50 | |     #[doc(fake_variadic)]
51 | |     impl_into_syscall,
52 | |     1,
...  |
55 | |     p
56 | | );
   | |_^
   |
   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
   = help: try referring to `all_tuples` crate for guidance on how handle this unexpected cfg
   = help: the macro `all_tuples` may come from an old version of the `variadics_please` crate, try updating your dependency with `cargo update -p variadics_please`
   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
   = note: `#[warn(unexpected_cfgs)]` on by default
   = note: this warning originates in the macro `all_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)

What went wrong

I think this cfg attribute may have been removed? I can't find anything about it outside of Bevy.

Additional information

Other information that can be used to further reproduce or isolate the problem.
This commonly includes:

  • screenshots
  • logs
  • theories about what might be going wrong
  • workarounds that you used
  • links to related bugs, PRs or discussions

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-BugSomething isn't workingC-DocumentationAn improvement to the documentation.S-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions