Cohadar once said something (within the first two pages of the TT thread off memory) about evaluating return-nothing boolexprs causing desynchs. So unless that is tested I don't consider it safe.
Then again, return-nothing and null are two different things. So I suppose it may be fine. I'd still want to see it tested, though.
(Obviously people do null boolexprs all the time. Problem is in evaluating a destroyed boolexpr, that handle may be reused, and you may try to evaluate a unit or something dumb or a newer boolexpr, which may execute code you didn't want to execute.)
Reddit, Slack, Google, Facebook, Instagram — these companies use our data — directly or indirectly — to train the next generation of AI language models. Yet, I don’t remember anyone asking our permission, and in doing so, these companies have proven the adage that customers’ data is their main...
Our new website went up early yesterday. Health Empowers You. 200 smoothie recipe guide and soon we will have detox, cognitive enhancement, weightloss teas and some coffee blends. https://healthempowersyou.net/products/smoothie-recipe-guide
It never fails that as soon as I say something about the bots they come back - this time they are under a whole new IP range - one thing in common though, Chinese!