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
My main motivation behind this is that MonteCarloMeasurements.jl already overloads these, so I believe this would make for better interchangeability between both approaches. Personally, I also find them more convenient to write than value and uncertainty, so it also might be worth then exporting them.
The text was updated successfully, but these errors were encountered:
This is interesting, but my fear is that one may accidentally strip the uncertainty out in generic code that doesn't know about Measurements, as mean would have a different semantic meaning for, say, Float64 and Measurement. Thus, I'm not really convinced this is a good idea.
My main motivation behind this is that MonteCarloMeasurements.jl already overloads these, so I believe this would make for better interchangeability between both approaches. Personally, I also find them more convenient to write than
value
anduncertainty
, so it also might be worth then exporting them.The text was updated successfully, but these errors were encountered: