Make some simple unit tests for the binder and set up some CI. Tests will be simple, standalone c++ headers that can be parsed and the output binding text can be compared to an expected output. Tests should include things that the current binder sometimes struggles with or where there are some hard-coded "hacks" like finding base types, dealing with heavily templated definitions, and anonymous enums and things like that. will also use it for for test-driven development for extending capabilities (write manually what the bindings should be for not yet supported things in the binder like arrays)
trelau
commented
4 years ago
Make some simple unit tests for the binder and set up some CI. Tests will be simple, standalone c++ headers that can be parsed and the output binding text can be compared to an expected output. Tests should include things that the current binder sometimes struggles with or where there are some hard-coded "hacks" like finding base types, dealing with heavily templated definitions, and anonymous enums and things like that. will also use it for for test-driven development for extending capabilities (write manually what the bindings should be for not yet supported things in the binder like arrays)