I'd want to see those "nested rulesets" that are causing the loss of error messages first.
Static is a no-go, because it breaks my multi-threading
Where I used "static" variables that could be problem here? Only static is `YamlErrorHandler` that is stateless.
And all `tree` objects get its own "handler" as global is only fallback if not overridden.
And code that crash without info look like:
reinforcements:
- type: firstwave
minTurn: 1
maxTurn: 1
maxRuns: 1
mapBlockFilterType: 1
spawnZLevels: [7]
randomizeZLevels: falsee #crash here without info where it is
this is code related to `AlienDeployment`, any `tryRead` will break line info as we call functions like
bool read(ryml::ConstNodeRef const& n, ReinforcementsData* val)
as now there is no `root` in sight. as alterative would be refactor all calls to propagate one pointer.
but as `yml::Callbacks` already need have pointer that we control, we could easy store here our `root`.