Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
can we maybe extend the pattern list in the filetype_extensions.conf used for the unittests on the fly?
We'd have to update
filetype_extensions.conf, run unit tests, and then revert back to the originalfiletype_extensions.conf. If someone interrupts the unit test by Ctrl+C, the original version wouldn't be restored which makes this approach a little fragile.
True that.
All other ideas coming to my mind are even more fragile or hacky or too complicated or all.
Not less ugly but more temporary:
There's always the option of a very elegant and permanent solution - not to have a unit test for meson at all :-)
:)
In the end, it might be a viable option when comparing costs and benefits.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.