Tests skipped unless I compile with opt-level = 0

[Maximetinu]

Hello

I found a situation where some gherkin given/when/then steps that should be visible are instead skipped

If I compile the tests without optimization -O0, then they are visible.

It's like the optimizations are stripping them away?

I reproduced it in a minimal example here:

https://github.com/Maximetinu/cucumber-multicrate-setup/tree/reproducing-cucumber-bug-see-latest-commit

This must be a bug on cucumber, because I can reach those functions from my code, but cucumber cannot. I would expect the same visibility for both.

Update: I made another branch on that repo where I tried to find the smallest possible commit introducing the bug. It is this: Maximetinu/cucumber-multicrate-setup@139ecc2

I don't know what conclusions to extract from it. It seems that the steps and the world context must be in the same mod in order for cucumber to find them?

Update 2: I noticed that what I'm trying to do is the same that is discussed in this thread: #236

@ilslv shared a repository showcasing how to set that up. I've also been able to reproduce it in that repository: Maximetinu/cucumber-steps-as-library@3a06dda

So, this bug is apparently caused by a combination of:

• using any opt-level > 0
• defining the cucumber world in a different file, separated from the steps

[tyranron]

@Maximetinu unfortunately, there is no much we can do from our side. We're just hitting the limitations of the upstream inventory crate we're using for collecting the defined step functions: dtolnay/inventory#50, dtolnay/inventory#52
Once they're resolved there, they will be automatically resolved in cucumber too.

Alternatives to the inventory crate were considered, but didn't solve the problem, since it rooted to the rustc/Cargo itself.