Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorder type parameters in the correct order #449

Merged
merged 4 commits into from
Jan 3, 2022
Merged

Reorder type parameters in the correct order #449

merged 4 commits into from
Jan 3, 2022

Conversation

tokatoka
Copy link
Member

@tokatoka tokatoka commented Jan 3, 2022

this pr sorts the type parameters

I skimmed through every impl and that was a pita 馃

@domenukk
Copy link
Member

domenukk commented Jan 3, 2022

I wonder if we could write a custom clippy lint for that :D

@tokatoka
Copy link
Member Author

tokatoka commented Jan 3, 2022

FeedbackLogic should come last, so I reverted that change.

@tokatoka tokatoka changed the title Reorder type parameter in the correct order Reorder type parameters in the correct order Jan 3, 2022
@domenukk
Copy link
Member

domenukk commented Jan 3, 2022

It doesn't have to be last, you just need to change the types here, too:

pub type EagerAndFeedback<A, B, I, S> = CombinedFeedback<A, B, I, S, LogicEagerAnd>;

@tokatoka
Copy link
Member Author

tokatoka commented Jan 3, 2022

Personally I feel it is a bit ugly to have CombinedFeedback<A, B, LogicEagerAnd, I, S> 馃槄
either way is ok

@domenukk
Copy link
Member

domenukk commented Jan 3, 2022

That's the price to pay for alphabetical ordering ;) We have the same situation in other places too:

pub type AflMapFeedback<FT, I, O, S, T> = MapFeedback<FT, I, DifferentIsNovel, O, OrReducer, S, T>;

@domenukk domenukk merged commit 674005f into main Jan 3, 2022
@domenukk domenukk deleted the alphabetical branch January 3, 2022 23:20
khang06 pushed a commit to khang06/LibAFL that referenced this pull request Oct 11, 2022
* alphabetical order

* revert

* revert

* fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants