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
Proposal: Implement the trigonometry functions: sin(), cos(), tan().
Current behavior: They are not implemented.
Desired behavior: They would be implemented.
Use case: Using the trigonometry functions.
Earlier versions of the query engine had a problem with implementing trigonometry functions because these would be a new class of functions labeled transform functions. A transform function gets parsed as a call, but it is effectively another binary operator so query validation works differently. Since earlier versions of the query parser relied on assuming that a call was a selector or an aggregator, this was difficult or impossible.
In 1.4, I changed the query compilation so this assumption is no longer made... as frequently. I think there are a few places where this assumption is still made, but they should be reasonably easy to remove and then we can implement the query engine to handle these calls as part of the normal processing of a binary operator.
The text was updated successfully, but these errors were encountered:
Feature Request
Proposal: Implement the trigonometry functions:
sin()
,cos()
,tan()
.Current behavior: They are not implemented.
Desired behavior: They would be implemented.
Use case: Using the trigonometry functions.
Earlier versions of the query engine had a problem with implementing trigonometry functions because these would be a new class of functions labeled transform functions. A transform function gets parsed as a call, but it is effectively another binary operator so query validation works differently. Since earlier versions of the query parser relied on assuming that a call was a selector or an aggregator, this was difficult or impossible.
In 1.4, I changed the query compilation so this assumption is no longer made... as frequently. I think there are a few places where this assumption is still made, but they should be reasonably easy to remove and then we can implement the query engine to handle these calls as part of the normal processing of a binary operator.
The text was updated successfully, but these errors were encountered: