Enumerator interface as contract

[ludo237]

Hello

I would like to propose this changes for Blender as my first contribution to this project, which I find interesting.

What is all about ?

This is the first implementation for a structure that allows enumerators to exists like in other programming languages such as c# or elixir.

The main goal is to provide a common layer for every future enumerators in order to use the same API across all the application.

Why matters ?

PHP does not have a good enumerator implementation. There are a lot of implementations of it but either they are old or they have been implemented in a weird way, without even tests.

Why bothering create a new one?

Enumerator are powerful and they need to be implemented with the best standard possible. I'm referring myself to .NET and Elixir in particular

Tasks

• [x] Add the ability to each enumerator to return an array of values that represent all the possible values of the enumerator itself.
• [x] Add some backup test for the initial implementation of this feature
• [x] Add new constant called _default that will retrieve the default value for the specific operator
• [ ] Improve the Enumerator interface in order to create a robust contract between the concrete classes

[freekmurze]

Hi,

thank you for this PR. My feeling is that if you want to build a modern enumerator it should be grown in package land and not inside Blender.

A good enumerator package is actually one our list with package ideas, but we haven't made one yet because other ideas were more important for our projects.