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.

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

provide common StateMachine impl for Flux and Mono #2647

Closed
OlegDokuka opened this issue Mar 12, 2021 · 2 comments
Closed

provide common StateMachine impl for Flux and Mono #2647

OlegDokuka opened this issue Mar 12, 2021 · 2 comments
Assignees
@OlegDokuka
Labels
status/need-design This needs more in depth design work type/enhancement A general enhancement

Comments

@OlegDokuka
Copy link
Contributor

OlegDokuka commented Mar 12, 2021 •
edited by simonbasle
Loading

Experiment with an abstraction that helps building the internals of operators, with bitmasks
@OlegDokuka OlegDokuka self-assigned this Mar 12, 2021
@reactorbot reactorbot added the ❓need-triage This issue needs triage, hasn't been looked at by a team member yet label Mar 12, 2021
@simonbasle simonbasle added status/need-design This needs more in depth design work type/enhancement A general enhancement and removed ❓need-triage This issue needs triage, hasn't been looked at by a team member yet labels Mar 15, 2021
@simonbasle simonbasle added this to the 3.4.x Backlog milestone Mar 15, 2021
@chemicL
Copy link
Member

chemicL commented Nov 30, 2023

Initial effort to include state machine to processors: #2626

@chemicL chemicL modified the milestones: 3.4.x Backlog, 3.7 Planning Mar 18, 2024
@chemicL
Copy link
Member

chemicL commented Jun 17, 2024

For the record, #3634 includes some general methods that could be extracted to a common class if needed in the future.

For now I'll close this issue as it has not been picked up for some time and re-writing existing mechanisms to use a new abstraction is not planned currently. If there's more work around these areas it would definitely be a nice-to-have.

@chemicL chemicL closed this as not planned Won't fix, can't repro, duplicate, stale Jun 17, 2024
@chemicL chemicL removed this from the 3.7 Planning milestone Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OlegDokuka OlegDokuka

Labels
status/need-design This needs more in depth design work type/enhancement A general enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chemicL @OlegDokuka @simonbasle @reactorbot