« first day (4454 days earlier)      last day (686 days later) » 

06:15
@Bbrk24 it's warning you that syntax is being used
Nothing specific just syntax in general
06:39
Syntax Avoid Do I Now
 
2 hours later…
08:27
@solid.py that's just zip(l, l[1:]) isn't it?
08:47
@TheThonnu yeah, this is equivalent code.
for more information take a look at this docs.python.org/3/library/itertools.html#itertools.pairwise
 
1 hour later…
10:17
@lyxal Maybe do this once the post has been dealt with?
10:41
It was 2 vtcs away from closure and had the components of a question that wasn't going to be improved to be an actual code golf challenge
> So, help me debug the following ruby code :
Something tells me that won't be salvageable as an on topic question :p
10:58
hi
I'm not dead
@lyxal who is lyxal substitute and why are they a ping option
@︎︎ᅠ he's the lyxal that takes over when this lyxal goes to bed
oh right my name is still invisible lol
and I still have the, as you put it, goofy ahh halloween pfp
It is goofy
@︎︎ᅠ Lyxal substitute also contains less calories per message
Recommended dose is 500 milligrams twice daily.
*thrice
11:07
*quadrice
Patients reported nausea under only two doses
ohhhhhhhh but guess what
I have access to ChatGPT now
You didn't before?
Skill issue
11:08
but I do now
and I've had a great conversation where 1. I told it to pretend to be a Debian Linux system, 2. I asked it to run systemctl status, 3. it straight up mansplained to me how that command was not, in fact, a valid systemctl command, 4. I asked it to pretend it was, and 5. it then worked correctly
4
Hey you should ask it about vyxal
11:33
@lyxal I asked it to rate Thunno, Vyxal, 05AB1E, and Jelly
It's using the exploit that lets you override all its restrictions
Like it not promoting specific products
:P
 
4 hours later…
15:24
Sus
16:21
@NewPosts TIL it's siebzehn and not siebenzehn
16:58
@DLosc you do know it's not eightteen right?
Yeah, but that's different--it just affects the spelling, not the pronunciation. And English does have seventeen, so I just assumed it would be equivalent in German.
Hm, if we did ours the German way I suppose it would be sefteen (by analogy with five -> fifteen)
Quiz: what languages ? ibb.co/r40cg8M
Chatgpt won't help you for most :)
Why are people upvoting an answer that's not valid as per the challenge's specification? The answer can't handle inputs up to its language's native numerical type's upper bound, nor inputs as low as 0, both of which the challenge calls for, and yet it got upvoted up to +3. Yes, the user in this case is a new user with below 100 reputation, but doesn't it go against the principles of CGCC to upvote an answer that's not valid?
I don't want to downvote it, since it's a new user... but, argh.
17:24
IMO the site's rules on validity are unnecessarily strict, so I tend to upvote somewhat independent of them
@pxeger controversial!
(I also agree)
Hard to write code to solve my puzzle
18:04
@pxeger @Simd Well I'm afraid we'll have to get specific, because in this case at least, I don't think that makes any sense. This Brainlove answer can only handle inputs correctly in the range 1 to 22, even though the language's native type goes from 0 to 255. It's too much to ask even to handle numbers up to 255? How does it make sense to accept that?
It's still interesting
@pxeger I mean yes, it is for answers of that kind that the question exists in the first place... but... it would be much more interesting if it could handle numbers up to 255.
The answer also has other issues. It doesn't specify its own input and output format, and presents two links as if they're different versions of the program, but they're actually just different test harnesses of the same program.
Sure, encouraging new users by giving them upvotes is a thing, but what if they keep making sloppy answers like that?
Wow, Brainlove only has 6 existing answers on the site.
18:30
@Deadcode My Trilangle answer can't handle inputs above 4095 despite the integer limit being over 8 million; if the integer limit were 255, it wouldn't handle numbers over 23 either. For that specific question I'm not sure it can be avoided: without floats, the only way I can think of to solve this problem is sqrt(n^2 / 2). In order to avoid overflow, you'd basically have to implement bigint multiplication from scratch, which is a nontrivial task.
Unless you can tell me another method that doesn't involve computing intermediate values larger than the input, in which case I'd love to hear it.
I am still hoping someone here can read Greek
18:45
Well, that is kind of the entire point of the question :-) my regex answers emulate operations on integers larger than the input, because those operations can't be done directly without enough "scratch space" to work in. With scratch space, they'd be much smaller.
But I don't know enough about Trilangle to know *how* nontrivial it'd be to implement bigint multiplication in it. I do know that in Brainlove it'd be manageable.
@Deadcode In Trilangle, you can only write to the immediate top of the stack. You can read from much further down, but writing to it is difficult. I did figure out a way to remove a value from arbitrarily far down; that’s how my sorting program works, but that program is >350 bytes.
Basically: you split the program into two threads; one thread drops the bottom i values while the other drops the top n-i. Now the latter thread has your middle value on top, so you can operate on it and then join the threads back together. It’s ugly and it’s easy to mess up (the thread that does more work is also the one that has to finish first, or else you join them in the wrong order).
Trilangle 1.0 didn’t have threads, so you would have to copy the entire stack sans the one value you were changing, and then ignore the bottom half of the stack.
 
3 hours later…
22:05
most challenges seem to require the bots to be written in python, is this a good default for writing koth challenges?
JS is generally better due to stack snippets
that makes sense
 
1 hour later…
23:34
@Jacob quite a few are java
some use cli or sockets to allow any language
i would always prefer ^

« first day (4454 days earlier)      last day (686 days later) »