Kai Ren

@JelteF I believe this has been fully covered by #182

@phip1611 bumping MSRV is OK, as we're going to release 1.0.0.

@ilslv for the reasoning it's slightly unclear what challenges/problems it allows us to solve? What we will be capable with it rather than without it?

@ilslv seems reasonable. I think we should give it a try at least.

@ilslv > My proposal is to wait until more tools will support it or until users of this library will actually ask for it. Or there will be a demand...

@theredfish I'm not sure whether it has sense. Flaky tests should not be a common thing. In our codebases we actively reworking them to remove any flakiness, because it's very...

@ilslv okay, I see that there are enough reasons for having this feature. Speaking of the feature design... > In addition to specifying number of times test should be retried,...

@ilslv yup. It also worths to mark the retried scenarios explicitly in the output, like the following: ``` Feature: Animal feature Scenario: If we feed a hungry cat it will...

@theredfish > What do you mean by separate branch? From the execution flow? It means [this](https://github.com/cucumber-rs/cucumber/issues/212#issuecomment-1118676320). > Then it will be a bit confusing with the existing feature replay_failed_tests no?...

@ilslv > Actually `@retry(3, after = 3s)` isn't possible, as tags don't allow spaces, so maybe we return to `@retry(3).after(3s)` I don't mind. > but I think the clearest way...