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
{{ message }}
This repository has been archived by the owner on May 26, 2021. It is now read-only.
Clarify effect of #156 in JavaDoc of concrete sub-classes. While AbstractQuantity in the absense of a concrete value still does a strict check, it should be noted, sub-classes can and usually do handle this in a more "semantic" way by checking the meanin of a value rather than its strict Java type.
Plus refining primitive comparison so only compatible types like "floating point" or "integer" ones get compared in a resource-effective manner.
The text was updated successfully, but these errors were encountered:
Clarify effect of #156 in JavaDoc of concrete sub-classes. While
AbstractQuantity
in the absense of a concrete value still does a strict check, it should be noted, sub-classes can and usually do handle this in a more "semantic" way by checking the meanin of a value rather than its strict Java type.Plus refining primitive comparison so only compatible types like "floating point" or "integer" ones get compared in a resource-effective manner.
The text was updated successfully, but these errors were encountered: