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
A current limitation of FloatTracker is that we can only inject NaNs after we have "infected" some numbers with a NaN. What if we were to have the option of entirely overriding the functions in Base—with the types that they have normally—to more aggressively (and automatically?) inject NaNs?
We might be able to do this with a macro: some kind of switch that controls what macros we emit, and then we can only emit that override code when the switch is flipped.
The text was updated successfully, but these errors were encountered:
A current limitation of FloatTracker is that we can only inject NaNs after we have "infected" some numbers with a NaN. What if we were to have the option of entirely overriding the functions in
Base
—with the types that they have normally—to more aggressively (and automatically?) inject NaNs?We might be able to do this with a macro: some kind of switch that controls what macros we emit, and then we can only emit that override code when the switch is flipped.
The text was updated successfully, but these errors were encountered: