yeah, Double and NaN, welcome to hell…

# announcements

[orangy]

yeah, Double and NaN, welcome to hell…

[groostav]

orangy: for those reading this is absolutely true, our "hardening" against NaN still includes a massive number of klooges that ultimately resulted in Double.MaxValue getting treated as a signal value in a couple places. One of these days I'm going to purge my codebase of this, but dealing with NaN's really is a pain in the butt