6 Matching Annotations
- Nov 2022
-
Local file Local file
-
Time Course and Recovery of Exacerbations inPatients with Chronic Obstructive Pulmonary Disease
Time Course and Recovery of Exacerbations in Patients with Chronic Obstructive Pulmonary Disease
-
-
Local file Local file
-
Early Therapy Improves Outcomes of Exacerbationsof Chronic Obstructive Pulmonary Disease
Early therapy improves outcomes of exacerbations of chronic obstructive pulmonary disease
-
-
Local file Local file
-
Pathophysiology of Exacerbations of ChronicObstructive Pulmonary Disease
Pathophysiology of Exacerbations of Chronic Obstructive Pulmonary Disease
-
-
Local file Local file
-
Predicting Severe Chronic Obstructive PulmonaryDisease Exacerbations
Predicting Severe Chronic Obstructive Pulmonary Disease Exacerbations
-
-
Local file Local file
-
An Index of Daily Step Count and Systemic Inflammation PredictsClinical Outcomes in Chronic Obstructive Pulmonary Disease
An Index of Daily Step Count and Systemic Inflammation Predicts Clinical Outcomes in Chronic Obstructive Pulmonary Disease
-
- Jul 2015
-
proquest.safaribooksonline.com proquest.safaribooksonline.com
-
Even though the value given to the match expression has the type Any, the data it is storing was created as an Int. The match expression was able to match based on the actual type of the value, not just on the type that it was given. Thus, the integer 12180, even when given as type Any, could be correctly recognized as an integer and formatted as such.
This is interesting and I believe quite different from how ATS handles types, aside from the fact that it can't match against non-algebraic datatypes. I think this is probably easier to understand as well, since it appears to not rely on constraint solving in order to determine types.
-