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

Revive APEX support #40

Closed
msimberg opened this issue Jan 19, 2022 · 0 comments · Fixed by #104
Closed

Revive APEX support #40

msimberg opened this issue Jan 19, 2022 · 0 comments · Fixed by #104
Assignees
Labels
effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: feature
Milestone

Comments

@msimberg
Copy link
Contributor

msimberg commented Jan 19, 2022

With the distributed functionality removed, the actual APEX support was removed. APEX can be turned into a direct dependency with no special support required on the APEX side and is quite straightforward to implement. I have some old working code for this already but from HPX. This needs to be revived.

@msimberg msimberg added effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: feature labels Jan 19, 2022
@msimberg msimberg added this to the 0.2.0 milestone Jan 19, 2022
@msimberg msimberg assigned aurianer and unassigned aurianer Feb 1, 2022
@msimberg msimberg self-assigned this Feb 8, 2022
@bors bors bot closed this as completed in c5c1644 Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: feature
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants