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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix model functions using SerializeIter #2955

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

GnomedDev
Copy link
Member

When passing SerializeIter in from outside, it counts as passing !Send over an await point and therefore making these functions unusable. This fixes that by moving the SerializeIter usage inside of Http, or replacing with a slice when necessary.

@github-actions github-actions bot added model Related to the `model` module. http Related to the `http` module. labels Aug 24, 2024
@arqunis arqunis added enhancement An improvement to Serenity. breaking change The public API is changed, resulting in miscompilations or unexpected new behaviour for users fix A solution to an existing bug. and removed enhancement An improvement to Serenity. labels Aug 26, 2024
@arqunis arqunis merged commit 849daf3 into serenity-rs:next Aug 26, 2024
21 checks passed
@GnomedDev GnomedDev deleted the fix-serializeiter branch August 26, 2024 23:18
GnomedDev added a commit to GnomedDev/serenity that referenced this pull request Oct 7, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
GnomedDev added a commit to GnomedDev/serenity that referenced this pull request Oct 20, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
GnomedDev added a commit that referenced this pull request Oct 20, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
arqunis pushed a commit that referenced this pull request Oct 28, 2024
This is a backport of #2955 to `current`. `bulk_ban` is currently uncallable
so this "breaking" change doesn't actually break anyone.
GnomedDev added a commit to GnomedDev/serenity that referenced this pull request Nov 11, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
GnomedDev added a commit that referenced this pull request Nov 13, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
GnomedDev added a commit to GnomedDev/serenity that referenced this pull request Nov 15, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
mkrasnitski pushed a commit to mkrasnitski/serenity that referenced this pull request Dec 8, 2024
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
arqunis pushed a commit to arqunis/serenity that referenced this pull request Jan 16, 2025
When passing `SerializeIter` in from outside, it counts as passing `!Send`
over an await point and therefore making these functions unusable.

This fixes that by moving the `SerializeIter` usage inside of `Http`, or
replacing with a slice when necessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change The public API is changed, resulting in miscompilations or unexpected new behaviour for users fix A solution to an existing bug. http Related to the `http` module. model Related to the `model` module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants