name clash/confusion

Hi 👋, I'm Ryan

🔭 I stole this template from Kartik.
💻 I spend my time writing the mlpack and ensmallen C++ machine learning libraries, and the bandicoot GPU linear algebra library.
💬 Ask me about how many things I've blown up in Kerbal Space Program.
📫 You can email me at [email protected].
⚡ Fun fact: it's not possible to beat Ryan at Mariokart. Go ahead and try.

www.ratml.org
my website, if you want to know more about me or read about strange projects I do

	If a custom callback is desired to take an action after any call
	to {\tt Evaluate()}, then only a {\tt bool Evaluate(...)} method is required
	to perform the desired action.
	\TODO{The name clash with two {\tt Evaluate()} functions
	is potentially confusing,
	especially to people not familiar with the codebase.
	Need to better differentiate the two functions,
	possibly via qualifiers.
	Need to explicit state which one is used by specific parts of ensmallen.
	Maybe {\tt Callback::Evaluate()} ?}

	The implementation of the function unpacks the {\tt callbacks},
	calling each callback's {\tt Evaluate()} method (if it exists) in sequence,
	and terminating early if any of these callbacks returns {\tt true}.
	\TODO{should this be ``false'' to indicate optimization failure?
	possible inconsistency/confusion with Fig.~\ref{fig:example_prog_callbacks_2};
	if this isn't an inconsistency, need to briefly explain why}