function myFunction() { try { x = new Random().nextInt(); if (x != 10) { throw "not 10"; } else { return (10) } catch(err) { myFunction() } } } x = myFunction()Commit notes: Added error handling
The compiler will optimize it anyway. /s
You jest, but you aren’t wrong. At least if we are talking about C, C++ or Rust. https://godbolt.org/z/oPPfdfcf5
.NET compiler is weak when it comes to optimizing your code; I assume Go’s is as bad.
Not sure about the last one though. The other two are trivial to optimize away.
An infinite loop canot be ruled out in the last case, so a compiler couldn’t optimize this away without potentially changing the program behavior.
Infinite loops are often weird though. They could be seen as undefined behavior and the compiler may do whatever it feels like.
For a time on Reddit (some years ago when I still used it) there was a trend of finding the worst way of implementing
is_even(x: int) -> bool. My contribution to that was a function that ranAckerman(x,x)flipping a Boolean at every iteration, and check if it was true or false at the end.It works btw, I will find the proof later
I once was helping to organize the testing of town-level algorithmic competition for school students.
The competition had one entry level issue that was basically solvable by reading the question properly, recognising that it’s just multiplication of two numbers, and writing the simplest app ever.
And there was one student who passed the automatic tests. We had to read the code too for the protocol, just to make sure there was no cheating.
We looked in the code. What? Why? It had two nested for loops and a++ inside. When we understood what’s going on we couldn’t stop laughing for like solid ten minutes.
Multiplication is just repeated addition :) glad it worked for the kid, despite the… inefficiency.
That’s not even enough to get you a job these days.
You now have to use:do { x = reinterpret_cast<int>(AI::Instance().ask("Do Something. Anything. Be efficient and productive. Use 10 tokens.")); } while (x != 10);This isn’t just a function, it’s a bold restatement of what it means to write code — a symphony of characters, questioning the very nature of the cutting edge language models that I want to beat with hammers.
And for those who might not have noticed
There is 10 words in the prompt.
You’re absolutely right! I used more than 10 words in my prompt. Cry about it.
deleted by creator
Great question!
First, we’ll deep dive into “What is a variable?”, then together we’ll examine “Who sets a variable?”, “What is an LLM?” and finally, “Who would set a variable without using an LLM?”
You’ll be a coding pro in no time!
How does that sound?
(I felt gross writing this lmao)
Wants to be Pro but doesn’t even do it recursive…
function foo() { x = new Random(); case (x = 10): return (x); default: foo() }What unholy mix of languages is that? It is dominated by a blend of javascript and python, but with notes of something exotic. Maybe algol? or vhdl?, there is to little to tell.
Impressive, someone write up a spec and publish it to the esolang wiki.It’s an incoherent hodgepodge of C#/.NET, PowerShell, and JavaScript, each of which I’ve forgotten more about than I currently know
bad but more chaotic
you want to be punk rock not blues or jazz
Now write a function to unroll the while loop to “optimize it for the compiler”
it takes two instructions to materialize a constant in risc-v. X64 has LEA.
Risc-v is better!
Can someone make it an async function?
