tag:blogger.com,1999:blog-3316231033424903659.post2413678895245078782..comments2024-01-08T10:34:23.606-05:00Comments on EcstasyLang: How to assert yourself morextclang (Ecstasy)http://www.blogger.com/profile/10099977807321312612noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3316231033424903659.post-75543579373786423532022-05-10T22:53:22.319-04:002022-05-10T22:53:22.319-04:00There are two solutions for sensitive applications...There are two solutions for sensitive applications:<br />1. An option to strip debug information when moving code to production<br />2. The use of a custom output for the assertion<br /><br />For example, this would include an account id in the exception details:<br /><br />assert account.id > 12345;<br /><br />But this would not:<br /><br />assert account.id > 12345 as "invalid account id";Cameronhttps://github.com/xtclang/xvm/noreply@blogger.comtag:blogger.com,1999:blog-3316231033424903659.post-68937767275360737242022-05-10T20:27:30.390-04:002022-05-10T20:27:30.390-04:00The value printed when an assertion fails could be...The value printed when an assertion fails could be sensitive information. Did you consider a method to hide certain values?Willnoreply@blogger.com