@Adám Nope, not until they have a user account here. Apparently the SO account on its own isn't enough to trigger, which is odd. I don't have their Chat Account info so I can't add them. Have them join here first, then I can extract their chat ID and add them that way
in names without spaces like HyperNeutrino only a diamond shows but it seems like either the last word, all but the first word, or a certain number of words depending on width get chopped off
@Razetime no it looks completely different because trying to use the full version is a real pain on a small screen and the old version didn't seem to fit very well
Codidact post, CGCC Sandbox, Codidact Sandbox
Given three positive integers as input, animate an ascii-art polygonal loading symbol on the screen.
Intro
You will be given three inputs, \$n\$, \$l\$, and \$d\$...
\$n\$ (one of \$3\$, \$4\$, \$6\$, or \$8\$), is the number of sides of a polygon:
...
Probably not originally, but it'd be not-too-hard to go through a few transpilations to more and more tarpit-like languages until you go from a python or JS solution to BF
If it takes a long time for naive solutions in languages with standard data structures (e.g. python), then how much longer would things take in a language which only works with cells?
BF solutions would probably have to run for quite a while to get an answer
I mean, only if you had the resources to build a chip on par with Intell or AMD, but poured those resources into optimising the limited subset of 8 instructions
But even then, the main optimization one would use is... more instructions.
Assuming the chip would be an 8 bit chip (As to handle the math), we'd be using a tiny fraction of possible instruction space
Another option would be to handle multiple instructions simultaneously with "Merged instructions"
"Given a list of seats, output all space cards where the fields aren't allergic to sea-monsters and fit together when rotated 82 degrees anti-clockwise. The answer is the index of the cup immediately left of the adapter with the most joltage multiplied by the three numbers that are found at random places in the weird input format."
and I still got the algorithm right pretty early, but didn't realize the GoL rule was wrong until I re-re-reread the instructions, losing 20 or so minutes
I primarily land on Code Golf by visiting links to questions from the Hot Network Questions roster. When I see comments on answers like:
Good observation!
or
Wow, impressive!
I tend to flag them as "no longer needed". This is in keeping with my understanding of how comments should work across...