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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Figure out a much better API for dedupe_map #73

Open

Pauan opened this issue Sep 8, 2023 · 0 comments

Assignees

Labels

breaking-change

Milestone

Owner

Pauan commented Sep 8, 2023

Right now this is the dedupe_map API:

signal.dedupe_map(move |new_value: &mut A| -> B {
    *new_value
})

But the user should be able to determine three things:

Whether the old value is equal to the new value or not.
What the new output value should be.
What the old stored value should be.

Pauan added the breaking-change label

Pauan added this to the 0.4 milestone

Pauan self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment