4 ms·
"Runtime analysis? How is that possible?" I thought... https://github.com/beatcode-official/server/blob/42169027dda3d0f0982ee56c39a295f54706be57/app/services/e
by user9999999999 2y ago
"Runtime analysis? How is that possible?" I thought...
https://github.com/beatcode-official/server/blob/42169027dda3d0f0982ee56c39a295f54706be57/app/services/execution/runtime_analysis.py https://github.com/beatcode-official/server/blob/42169027dda...
- bean-weevil 2y agoLmao. They need to call that out so the users know not to believe it
- deleted 2y ago[deleted]
- Aurornis 2y agoClarifying that it’s the output of an LLM is responsible. Though LLMs are really good at anything related to plain LeetCode problems. There has been so much written about the standard LeetCode problems across so many websites that it’s all heavily represented in training sets.
- ericye16 2y agolmao, halting problem solved with one weird trick!
- dudus 2y agoMore and more I find code like this. When you dig into an interesting aspect it's just an llm call. I haven't decided yet if it's good or bad. But it does seem to work a most of the time. The problem is that we're used to code that works all the time or none of the time. With LLMs you can't know if it's right for sure and it's really hard to check.
- weebao 2y agoYeah sorry :) At first I tried to do a stress test, then plot a curve and try to find the closest runtime curve to that curve but it didn't work most of the time ;-;