The interpreter tries to catch any exception and add the latest node information to it, but currently we only used that to print better formatted error messages on MesonException. Since we should theoretically have that property for most/all exceptions, let's percolate that upward, and message the user that an unexpected traceback was encountered, that it should be reported as a bug, and the helpful information of "how far into parsing this meson.build did we get before erroring out, anyway?"pull/9664/head
parent
bea735dd76
commit
3c039f42a0
1 changed files with 8 additions and 2 deletions
Loading…
Reference in new issue