Hey there! Sorry for not answer before, I move out from my country and haven’t been on a PC since the day I posted this.
About the questions, I’ll try to answer as best as I can remember, but we can talk later on DC if I’m wrong about it :)
-
The 256 should only be the limit of instances to index at the same time, so, if you have more than 256 instances of “oWall”, then looking for an specific wall would be a pain, but if you are looking for oPlayer, as soon as you write “oP” the oPlayer instance should pop in (if there’s no 256 “oP” instances before it).
-
I have thought about it when I was developing the feature, but I’m still not sure how to implement it, I thought on some possible implementations but yours seems very reasonable, what I could think now is:
- An extra callback parameter for ArgumentWithOptions constructor. But this would mean to create a new parameter for JSON files.
- A new ArgumentWithDynamicOptions constructor. This may change the Argument struct.
- A rework of the Argument constructors leaving on one “Argument” constructor, but using a enum of types (DEFAULT, WITH_OPTIONS, DYNAMIC_OPTIONS, etc) to simplify everything in one struct.
Btw, would love to have contributors to the project! Thank you for your interest, I may not be too responsive these first weeks, but I would love to have a chat with you, will add you to DC nos :)