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.)
I'm on a page about incorrect corrections, and spent the better part of like two hours trying to get someone to understand that -5^2 = -25, not 25, and then that post had comments get reposted because that group is self sustaining, and that person was in turn trying to explain what I just explained to them. And I'm taking that as a victory
I will be AFK for a couple of days you guys hold down the fort while I am gone. I will be checking in on my phone but that will severly limit me. Be back saturday!
I just got to watch the video because even though I was there I was trying to work out tech problems with the chat since I was the social media guy so I was distracted but check it out guys the video is super fucking great!