Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upTime.every improvement #884
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Jul 13, 2017
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Jul 13, 2017
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Jul 13, 2017
Member
It may make sense, but any design like this would need to be motivated by practical examples. If you have some of those, that can make a stronger suggestion. I'd recommend trying to refine the idea on Elm slack or the elm-discuss mailing list and opening a new issue if you feel you have compelling evidence.
|
It may make sense, but any design like this would need to be motivated by practical examples. If you have some of those, that can make a stronger suggestion. I'd recommend trying to refine the idea on Elm slack or the elm-discuss mailing list and opening a new issue if you feel you have compelling evidence. |
evancz
closed this
Jul 13, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Jul 13, 2017
Contributor
@kuznero, there are related questions for other "subscription generating functions". So it might be useful for you to have a look at:
as well as at two existing mailing list threads (referenced over there):
|
@kuznero, there are related questions for other "subscription generating functions". So it might be useful for you to have a look at: as well as at two existing mailing list threads (referenced over there): |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kuznero
commented
Jul 14, 2017
|
@jvoigtlaender thanks for the links |
kuznero commentedJul 13, 2017
Does it make sense to improve current
every : Time -> (Time -> msg) -> Sub msgtoevery : Time -> (Time -> Maybe msg) -> Sub msg, such that event is fired not precisely everyNsomething, but also does that based on some predicate that will be possible to implement inTime -> Maybe msglambda?