add #[must_use] to generate function

[enaut]

The clippy lint https://rust-lang.github.io/rust-clippy/master/index.html#must_use_candidate suggest that this function should have a must use flag - it does seem sensible to me. - but please verify this does not break anything.

[kilork]

Hey, this sounds reasonable.

I need to check, how it would play with the scenario, which I personally use a lot: a crate which serves only one target - to collect resources and export single function, which would be later used in another crate.

If it goes well, I think it is good idea to add it, but probably I would just add it without merging this PR, because I already reworked this part of code.

[enaut]

No problem... if you choose to not make it must_use please add an #[allow(clippy::must_use_candidate)] so that the generated code produces no warnings on strict clippy settings like -Wclippy::pedantic -Wclippy::nursery -Wclippy::cargo -Wclippy::all.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[enaut]

Do you still need anything or should I close the PR?

[kilork]

I created a separate issue #44 to track this for 3.1.0. Really have almost no time last months, sorry for this :( You can close this PR as we have tracking issue instead and 3.1.0 is very different to current version.

[enaut]

Ok thanks no worries