Dylan Baker
Some tests are about the output of the libarary, some are only about the validity. Using json.load will test the validity for us.
This one is actually rather annoying to think about, as it's complex control flow. I think, since `foreach` is determanisticly sized, we can basically implement it as something like: ```...
`subdir` is a pain. Ideally, we'd deal with it entirely at the AST level, because you'd have `subdir('foo')`. No variables, no keywords, just a basic "here is a subdir". We...
I was thinking about this because Visual Studio supports this natively. It's a really hard problem for the reference implementation because of it's implementation details, but I think we could...
if you have something like ```meson files(files(files(files('foo'))) ``` It currently takes four loops to resolve this, because the evaluation order is from outside to inside (the simplest solution). However, by...
the dependency() function is super important to any meson implementation, Meson++ will need to implement one for gtest, which comes with the added bonus of being a specially handled dependency.
Currently the error messges have no location data, which is very annoying and not very useful.
This optimization allows more find_program calls to be handled in the single threaded loop than requiring additional calls to find_program later.
Which is likely more complicated than basic types.