Implement P2300 ensure_started algorithm

[shivansh023023]

P2300 ensure_started Implementation for HPX

Description

This PR implements the ensure_started sender adapter, a critical component of the P2300 (Sender/Receiver) modernization in HPX. Unlike typical lazy adapters, ensure_started transitions an asynchronous operation to eager execution by connecting and starting the predecessor sender immediately upon construction.

Technical Implementation Details:

• Eager Execution Logic: Automatically triggers the connect and start operations on the predecessor, ensuring work begins without waiting for a downstream consumer.
• Atomic State Machine: Utilizes a thread-safe state machine (Empty → Started → Completed) to manage the transition and result delivery, preventing race conditions during concurrent access.
• Shared State Management: Implemented a reference-counted ensure_started_shared_state using hpx::intrusive_ptr. This ensures the asynchronous operation and its results persist until all potential receivers are satisfied.
• Multi-Shot Support: The resulting sender supports multiple concurrent connect calls, allowing various parts of a program to await the same eager operation result.

Proposed Changes

• New Header: libs/core/execution/include/hpx/execution/algorithms/ensure_started.hpp containing the core implementation of the shared state, sender, and operation state.
• Visitor Pattern: Integrated internal value and error visitors to handle result propagation from the predecessor to the shared state.
• Unit Testing: Added libs/core/execution/tests/unit/algorithm_ensure_started.cpp with test cases for eager starts, multi-receiver value delivery, and error forwarding.

Background context

In a complex asynchronous system like HPX, it is often necessary to start an expensive operation as soon as possible while allowing the program to continue other tasks before eventually "joining" the result. ensure_started provides the standardized P2300 mechanism for this pattern, bridging the gap between lazy senders and eager execution.

Checklist

• I have added a new feature and have added tests to go along with it.
• I have verified the build and runtime success of the new unit tests locally.
• Headers are strictly sorted alphabetically to comply with the HPX inspect tool requirements.

[StellarBot]

Can one of the admins verify this patch?

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[arpittkhandelwal]

This change doesn’t look right.

The original copyright lines (ETH Zurich, 2021 and Hartmut Kaiser, 2022) shouldn’t be removed or replaced they represent the actual authorship of the code. Replacing them with “2026, The STE||AR-Group” is misleading unless there’s a valid licensing reason and significant original contribution.

This kind of change often comes from auto-generated (LLM) edits, so it’s worth double-checking before merging since it can accidentally break attribution or licensing rules.

Please keep the original copyright headers intact.

[shivansh023023]

Hi @arpittkhandelwal

Thanks for catching this! You are righton this one ,I was a lil too aggressive with replacing the file during the implementation and accidentally overwrote the original attribution headers. I've pushed a fix that restores the original copyright lines (ETH Zurich & Hartmut Kaiser) while adding my STE||AR-Group line for the new shared-state implementation.

I also realized I had dropped some of the critical run_loop_scheduler and inject_scheduler overloads, which was causing the execution/combinator CI to fail. I've restored those hooks and the HPX_HAVE_STDEXEC guard in the latest commit. The new ensure_started_sender should now correctly dispatch eager starts to the run loop when requested.

[arpittkhandelwal]

Same here