add info on meson IntrospectionInterpreter

README.md

···
 
 Clearly, the syntax of build recipe files is complex enough to require actual parsing and evaluation.
 
-Such a static analysis of build recipes is possible, though. Lightweight parsers for build recipes already exist, such
-as [parse.c][muon-parser] from [muon][muon], which is a lightweight Meson implementation. Such a parser could be used to
-turn build recipes into [AST][ast]s, which can then be evaluated using custom rules that do nothing but collect
-the names of all dependencies referred to in the build recipe.
+Such a static analysis of build recipes is possible, though. Lightweight interpreters for build recipes already exist,
+such as [parse.c][muon-parser] from [muon][muon], which is a lightweight Meson implementation. In fact, meson itself
+provides an [IntrospectionInterpreter][meson-introspection] capable of identifying dependencies. Such interpreters could
+be used to turn build recipes into [AST][ast]s, which can then be evaluated using custom rules that do nothing but
+collect the names of all dependencies referred to in the build recipe.
 
 Of course, such a parser-evaluator would have to be written for each build system, but once the most popular build
 systems, such as CMake and Meson, are covered, it seems likely that the dependencies of a good proportion of C/C++
···
 [linker]: https://en.wikipedia.org/wiki/Linker_(computing)
 [meson-deps]: https://mesonbuild.com/Dependencies.html
 [meson-file]: https://github.com/numpy/numpy/blob/main/numpy/meson.build
+[meson-introspection]: https://github.com/mesonbuild/meson/blob/master/mesonbuild/ast/introspection.py
 [meson]: https://mesonbuild.com/
 [mkl]: https://docs.cirrus.ac.uk/software-libraries/intel_mkl/
 [muon-parser]: https://git.sr.ht/~lattis/muon/tree/master/item/src/lang/parser.c