-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limitation of Streams in the past [General discussion] #23
Comments
Interesting cases: Perhaps you could come up with a couple of simple use cases ... e.g. predicting tomorrow's weather (it can be a dumb predictor that just predicts the same as today), and see what the consequence of removing that constraint would be. To be honest I think the main reason it's there at the moment is just to protect the user from unintentional mistakes, as this was the most common cause. It's worth noting that by default I think all of the channels are valid up to |
What are the implications of using Streams of data with a timestamp in the Future (or in the present moment)?
At this moment, if you ask for a Stream to be computed for the current time it will raise the following Exception
I can think of two cases where it could be interesting to allow Streams in the future:
The text was updated successfully, but these errors were encountered: