Replies: 7 comments
-
One tip that helped me was that for very large inputs, the stack frame memory could potentially overflow due to too many recursive calls. Perhaps making the functions tail-recursive could help? |
Beta Was this translation helpful? Give feedback.
-
Finally 300/300! In fact, according to my experience, 281/300 is not due to code's running time, but your advice is helpful enough to even help me deal with some future assignments. Thank you! |
Beta Was this translation helpful? Give feedback.
-
@frogfrog2 |
Beta Was this translation helpful? Give feedback.
-
My problem was to assume that something is always true. |
Beta Was this translation helpful? Give feedback.
-
I'm having the same problem right now :( Can we assume that the given parameters are correct? Meaning can we assume that the input parameters are not in unexpected form (e.g. wrong padding, etc.)? If we can't safely assume the conditions, what do we need to return in those cases? |
Beta Was this translation helpful? Give feedback.
-
Input text has no such problems. I think you can find the assumption in the lecture note. |
Beta Was this translation helpful? Give feedback.
-
I just figured out the error. Thank you for sharing your experience! It really did help. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Name: Jihwan Park
Hello, I'm fixing my code again and again to reduce its running time. Even though it becomes much more efficient than my first attempt, there is NO change in my score.
Does anyone know whether 281/300 is due to running time limits?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions