Commit graph

17 commits

Author SHA1 Message Date
Ilya Kantor
c799f28d2e minor fixes 2020-05-06 23:36:02 +03:00
Ilya Kantor
83c07e100a minor fixes 2020-05-06 23:34:02 +03:00
Ilya Kantor
08309a07f6 minor fixes 2020-05-06 23:24:22 +03:00
Ilya Kantor
6cf15b78bc minor fixes 2020-05-06 23:23:31 +03:00
Ilya Kantor
9bd640c414 minor fixes 2020-05-06 23:22:40 +03:00
Ilya Kantor
fc2ba214e8 minor fixes 2020-05-06 23:22:14 +03:00
Ilya Kantor
df6f6be420 minor fixes 2020-05-06 23:21:13 +03:00
Ilya Kantor
3440a4eb80 minor fixes 2020-05-06 23:19:55 +03:00
Ilya Kantor
0444de2a00 minor fixes 2020-05-06 22:46:26 +03:00
Ilya Kantor
458493781f minor fixes 2020-05-06 20:57:42 +03:00
Ilya Kantor
844b96a821 fix debounce 2020-05-06 20:35:58 +03:00
Ilya Kantor
80f2becc95 fix debounce 2020-05-06 20:29:17 +03:00
Ilya Kantor
cd5a7e451f fix debounce 2020-05-06 20:27:34 +03:00
Artur Haurylkevich
ee80b55a1b
add test case for debounce 2019-10-17 22:01:44 +03:00
paroche
cdde99fd19
Update task.md
Wording was ungrammatical and hard to understand. I made my best guess as to what you want to say. However, it is not clear from the description or the examples whether the debounce wrapper should inhibit calls attempted ms milliseconds after the last call that wasn't ignored, or ms milliseconds after the last call that was attempted, even if it was ignored. I would think it would be the former, but the example could go either way. If the f(4) example used 1000 or 1001 ms and still runs, that would clear it up. If it has to be 1100 like it is, that would suggest that it's the second scenario above. In my propsed change I preserved the ambiguity.
2019-09-02 19:49:54 -06:00
Ilya Kantor
408ba7d4e4 make sure a solution always shows up, use "demo" if exists 2019-02-21 19:35:04 +03:00
Ilya Kantor
97c8f22bbb up 2017-03-21 17:14:05 +03:00