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
At the moment, when having a parsed CRON expression and selecting one of its fields by it's CronField type, the return type is a path-dependent type result of the machinery used to do this selection in a type-safe way:
In the first case, the path-dependent type is an useless artifact since right after obtaining the reference to the field, we can't do much more with other than printing it's expression.
The type of field[CronField] should unify to the actual type of the node, otherwise that operation has very little sense to exist.
The text was updated successfully, but these errors were encountered:
At the moment, when having a parsed CRON expression and selecting one of its fields by it's
CronField
type, the return type is a path-dependent type result of the machinery used to do this selection in a type-safe way:This in contrast to the return type obtained when selecting by the field accessor:
In the first case, the path-dependent type is an useless artifact since right after obtaining the reference to the field, we can't do much more with other than printing it's expression.
The type of
field[CronField]
should unify to the actual type of the node, otherwise that operation has very little sense to exist.The text was updated successfully, but these errors were encountered: