Eliminate runtime reflection in Operators

[JaredDavis22]

Eliminate reflection during runtime. A test is added to ensure the manually maintained list in Operators remains in sync with the declared Operator entries.

[ctrueden]

What is the rationale for this change? Does it improve performance? It is a net increase of 42 lines of code, and makes the codebase less DRY. Is it just because people consider reflection to be ugly or ill-advised? If the issue is that repeated calls to standardList() are not cached, it would be less code to keep the new private static List<Operator> operatorList populated lazily at the first call to standardList().

[ctrueden]

See also related discussion at #24 (comment), which explains that this change does improve performance. But if we cache the calculated-via-reflection list, I feel like that should achieve the vast majority of the performance gain. (Is standardList() being called more than once?)

[JaredDavis22]

When we can shift anything from runtime to compile time, we should. Reflection can be made to hit less. But, it will always be an unnecessary hit.

Eliminating reflection from the main code makes the project easier to understand imho. When you see the list, you know what is going on. The test code reflection will remind the programmer if they added an operator but did not add it to the list.

GraalVM may or may not work as is with the reflection. I know it will work 100% with the list approach.

How often has the list changed over the years?

[ctrueden]

@JaredDavis22 I found a way of doing what you want here, without explicitly replicating the list of operators. Please take a look and let me know what you think. If you like it, I'll merge this.

[JaredDavis22]

Looks great. Thanks. Do we still need reflection in OperatorsTest with this solution?

[ctrueden]

Do we still need reflection in OperatorsTest with this solution?

Nah, I think we're OK without it!