Ben Wiederhake 6e5f7b7ea3 remove 'complete' feature flag, make it unconditional ...

This avoids using cfg with the destination-crate's feature "complete"
in proc-macro "derive".

Quoting cargo:

    using a cfg inside a derive macro will use the cfgs from the
    destination crate and not the ones from the defining crate

In these two instances, the cfg was simply used to avoid emitting dead
code if the "complete" feature is not desired. By passing the "complete"
feature down to the derive crate and evaluating if there, we achieve the
same goal, without having to deal with suprisingly-valued and unexpected
cfgs downstream.

Alternatively, we could just evaluate the flag inside the derive crate,
and pass the feature flag to it.

2025-04-12 22:20:32 +02:00

..

workflows

remove 'complete' feature flag, make it unconditional

2025-04-12 22:20:32 +02:00