Kenny Weiss

Issue #1058 will switch axom over from MPI-3 shared memory to Umpire's shared memory. In either event, we should have at least one CI job that exercises shared memory.

We suspect this is somehow related to our usage of object libraries. We should revisit this issue after removing object libraries in #1057.

We might also want to output/input triangle meshes in the blueprint format for In/Out, distance and shaping queries

Closing this issue. Will create a new one to move to compilers from shared radiuss-spack configs.

We should investigate if type aliases can be marked as deprecated. If so, we should mark these as deprecated (to be removed in the release after the current one), and...

If we did this, we'd likely need to have a convention for how to assign the different levels, e.g. what differentiates a "level 2" message from a "level 3" message?

This doesn't appear to be a high priority. Let's revisit if/when needed.

https://github.com/LLNL/axom/issues/798

Thanks for posting this @Destranix. We typically use the `blt_append_custom_compiler_flag()` macro to set flags for a specific compiler family, e.g. `MSVC` and `MSVC_INTEL` on Windows. Are these providing the wrong...

Thanks for reporting this, @adayton1. We have several indirect test cases for this functionality via `primal::squared_distance(Point, Triangle)`, which is defined in terms of `closest_point` -- but we should add explicit...