Mikael Simberg

Compile-only tests are not handled correctly when using an installed HPX for tests

2

This is to follow up on #4335 which added support to use an installed HPX for tests.

Broadcast and scatter hang with only one locality

1

See discussion starting at https://github.com/STEllAR-GROUP/hpx/pull/4771#discussion_r443368822.

Bulk task operations

4

While going through open issues (#4227 and this comment specfically: https://github.com/STEllAR-GROUP/hpx/issues/4227#issuecomment-555616764) I was reminded that the Moodycamel queue supports batched operations. I think we should definitely start using this. We...

Formalize public API, namespace, and release policy

3

I'd like to see us have at most two levels of nesting in namespaces: a top-level `hpx` and `hpx::modulename`. I'd even slightly prefer having everything in the public API be...

Fix failing Windows and macOS tests

1

We do not currently have perfect test runs on Windows and macOS. Tests that we know fail have been added to blacklists in the GitHub actions workflow files ([Windows](https://github.com/STEllAR-GROUP/hpx/blob/master/.github/workflows/windows.yml) and...

Static linking fails during CMake configuration

5

When setting `-DHPX_WITH_STATIC_LINKING=ON` CMake configuration fails at the end with ``` -- Configuring done CMake Error: install(EXPORT "HPXTargets" ...) includes target "hpx" which requires target "hpx_assertion" that is not in...

HPX module "configurations"

2

This issue is for discussing if and how to expose modules to users: - size of modules; small *and* large? - static/dynamic? - build configurations?

Add assertion macros that print their values

6

Having alternative assertion macros in the style of ``` HPX_ASSERT_EQ(x, 3); ``` which print the value of `x` when the assertion fails would be nice to have to make debugging...