You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In parse.cpp we have methods "user_warning" and "debug_warning", which are intended to be used when there is a break in specification from the Chapter 3 processing level.
Right now methods are empty, so warnings are swallowed.
We also need consistent model of errors/warnings/infos/debugs to not overload user with a lot of broken, but recoverable, specification (which user probably doesn't really care about and doesn't know what to do with), but do not bury it and give user access to it on request.
Some tests in test_parse would expect these warnings.
The text was updated successfully, but these errors were encountered:
In parse.cpp we have methods "
user_warning
" and "debug_warning
", which are intended to be used when there is a break in specification from the Chapter 3 processing level.Right now methods are empty, so warnings are swallowed.
We also need consistent model of errors/warnings/infos/debugs to not overload user with a lot of broken, but recoverable, specification (which user probably doesn't really care about and doesn't know what to do with), but do not bury it and give user access to it on request.
Some tests in
test_parse
would expect these warnings.The text was updated successfully, but these errors were encountered: