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

feat(hydroflow): [Tracking Issue] Hydroflow engine upgrade to support flo #1500

Open
1 of 7 tasks
MingweiSamuel opened this issue Oct 21, 2024 · 0 comments
Open
1 of 7 tasks
Assignees
Labels
core api hydroflow excepting the surface syntax hydroflow syntax Hydroflow's custom surface syntax P0 Highest priority performance scheduler Something with the scheduler (part of the Core API)

Comments

@MingweiSamuel
Copy link
Member

MingweiSamuel commented Oct 21, 2024

Driven by hydroflow+ / flo-semantics requirements


(docs)

@MingweiSamuel MingweiSamuel added hydroflow syntax Hydroflow's custom surface syntax performance core api hydroflow excepting the surface syntax labels Oct 21, 2024
@MingweiSamuel MingweiSamuel self-assigned this Oct 21, 2024
@MingweiSamuel MingweiSamuel added the P0 Highest priority label Oct 21, 2024
@MingweiSamuel MingweiSamuel added this to the 1.0 Release milestone Nov 12, 2024
@MingweiSamuel MingweiSamuel changed the title Hydroflow engine redesign feat(hydroflow): Hydroflow engine upgrade to support flo Nov 21, 2024
@MingweiSamuel MingweiSamuel added the scheduler Something with the scheduler (part of the Core API) label Nov 21, 2024
@MingweiSamuel MingweiSamuel changed the title feat(hydroflow): Hydroflow engine upgrade to support flo feat(hydroflow): [Tracking Issue] Hydroflow engine upgrade to support flo Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core api hydroflow excepting the surface syntax hydroflow syntax Hydroflow's custom surface syntax P0 Highest priority performance scheduler Something with the scheduler (part of the Core API)
Projects
None yet
Development

No branches or pull requests

1 participant