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
In short, yes. However Kind is a pretty ugly wart in uom right now. See discussion in #313. Any multiplication or division loses kind information and defaults back to uom::Kind.
Thank you!
Now I see why it is non-trivial to implement Entropy [J/K] and Molar Entropy [J/(K/*mol)] quantities, having the same dimension as heat capacity and molar heat capacity, but with absolute temperature instead of temperature interval.
Without specifying TemperatureKind they conflict with heat capacity and molar heat capacity.
With TemperatureKind -- they fail with mismatched type error since the kind disappears in all equatiuons like
dS = dQ[Energy]/T[AbsoluteTemperature]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding temperature gradient quantity [TemperatureInterval / Length], with base unit Kelvin / meter.
I've checked that it returns TemperatureInterval when multiplied by length:
let tgrad = TemperatureGradient::new::<kelvin_per_meter>(1.0);let l = Length::new::<meter>(2.0);let t_int: TemperatureInterval = tgrad * l;// okand fails (as it should) when trying to assign to ThermodynamicTemperature:
let t_abs: ThermodynamicTemperature = tgrad * l;// error[E0308]: mismatched types, ^^^^^^^^^ expected traitTemperatureKind, found traitKindIs just not providing "TempertureKind" a correct way of declaring quantities containing temperature interval in their dimension?