Display first cause of AggregateException in stacktraces

Currently if an uncaught AggregateException is thrown, the stacktrace shows no cause and the stacktrace points to the creation of AggregateException.

Now it'll display the first exception in the list of causes in the stacktrace as the cause to allow developers to debug their application, even if they can only do it one at a time...
Should we maybe wrap other throwables in a RuntimeException here? Or throw a new RuntimeException? Seems inadvisable to just ignore an error. Someone who's already using this might see an AggregateException with no causes.