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
Currently in order to improve some of our error messages like in #14554 we pay a double cost in order to leverage runInDebug. In some future state we should be able to use a "feature flag" which allows us to strip things without needing to call it twice and so we can leave the code run in context. That would look something like this:
if(isDebugBuild()){// Do the useful debug thing, probably including try/catch.}else{// Do the performant thing.}
Do we wish to add a "feature flag" like this? Related though to if (testing) , it is a tremendous way to accidentally troll ourselves.
Currently in order to improve some of our error messages like in #14554 we pay a double cost in order to leverage
runInDebug
. In some future state we should be able to use a "feature flag" which allows us to strip things without needing to call it twice and so we can leave the code run in context. That would look something like this:Do we wish to add a "feature flag" like this? Related though to
if (testing)
, it is a tremendous way to accidentally troll ourselves./cc @krisselden @rwjblue
The text was updated successfully, but these errors were encountered: