Avoid using exceptions (like NATSTimeoutException) for flow control

[robertmircea]

I've noticed through nats.net code base that exceptions are consistently used for managing flow control for certain functions like JetStreamAbstractSyncSubscription.NextMessage(int timeout). As far as I know, using exception for flow control and, especially, in tight loops like the ones which use NextMessage is considered bad practices with performance implications.

https://docs.microsoft.com/en-us/previous-versions/msp-n-p/ff647790(v=pandp.10)#do-not-use-exceptions-to-control-application-flow

For example, NextMessage throws NATSTimeoutException when no more message could be fetched. Would it be possible to offer overloaded signatures which do not throw exceptions?

public bool NextMessage(int timeout, out Msg m)

or better (to be consistent with .NET Core framework conventions)

public bool TryGetNextMessage(int timeout, out Msg m)

This function would return false instead of throwing NATSTimeoutException and true when a message is available and will be returned as out parameter.