Mikael Simberg

Ugh, thanks @eschnett for pointing this out. Does this come from things in `/core/src/HPX/...` being installed directly into `/HPX/...`? That seems like a source of trouble for other Kokkos directories...

Relevant: https://github.com/kokkos/kokkos/issues/4857 and https://github.com/kokkos/kokkos/issues/4856.

> What about the `hpx::apply` `std::apply` semantic mismatch? Should we start deprecating `hpx::apply` for some other name (`hpx::fire_n_forget`/`hpx::post`?) so we can substitute our `hpx::util::invoke_fused` with `std::apply` without causing undue confusion?...

I'd like to go ahead and remove the thread compatibility layer as there should be support for it everywhere (and it's off by default). Are there actually platforms where we...

I think we can all agree that this is not going to be straightforward. This is *never* going to happen if we have to find full replacements for all the...

> Disabling the timer-pools, while they are already optional (are they?), would disable all timed operations (`sleep_until`, etc.). But we might be able to rig up some alternative timer support....

A complete list of Boost dependencies with incomplete annotations: https://gist.github.com/msimberg/3a1b4273297ce931717262bcf094f011.

I added the list of boost headers to to main issue description where we can keep track of what to do and what has been done about the different dependencies....

@tapaswenipathak feel free to work on this. My comment above to @kshitij12345 applies to you as well. The miscellaneous section is a good place to start.

@felicepantaleo @Element-126 @rishabhkumar296 Just checking to see if there has been any progress on this? We're planning a release in the next few months and wondering if anything could make...