rob
08/23/2026, 10:35 AMVaibhav (BAML 🐑)
08/23/2026, 5:28 PMreflect.Package.compile(<code>)
we are currently thinking about making a clippy equivalent (linter) that can be extendable by BAML defined code and as a part of that, i suspect we'd expose AST + typechecking functions directly in BAML so you can parse various things.Vaibhav (BAML 🐑)
08/23/2026, 5:29 PMbaml-sam
08/23/2026, 10:43 PMbaml-sam
08/23/2026, 10:44 PMrob
08/24/2026, 9:52 AMbaml-sam
08/25/2026, 6:23 PMbaml describe and baml lsp , there's quite a lot of work that's gone into the compiler to produce well-defined symbols. Re-implementing that yourself would be challenging to get right reliably.
The first few compiler phases are relatively stable at this point - there are some things that are still evolving - but between the two options of
1. rolling your own TS parser/lexer + IR + type checker to get something that works on 70% of code, and
2. reusing the production BAML toolchain internals that works on 99% of code, and updating it when BAML compiler internals change
I think (2) is a more attractive maintenance burden for you, even if we can't make promises about the AST stabilityrob
09/04/2026, 2:12 PM