rickrolling is fine and all (otherwise i would've booted lyxal long ago :P) but just don't be disruptive about it. it's a pretty innocent joke but people have been suspended from chat for upwards of a year before (granted, their signal:noise ratio was considerably bad and moderation back then was more strict than now, at least IMHO)
> Working with a prefix sum array (an array where the ith value represents the sum of the first i values in the underlying data), access and summation are O(n), but modification is O(n).
We currently have four tags about up/down-voting:
down-votes
up-votes
voting
votes
There's an argument to be made for keeping down-votes separate since there's a bit of stuff about downvoting culture specifically which isn't necessarily related to the voting mechanism as a whole. However, brows...
Don't promote your own content too much. Promoting your own content is absolutely OK, but there is definitely a point at which it becomes excessive. Avoid promoting off-site material unless it's related to the topic of discussion. Sharing posts that you want feedback on is perfectly fine, but sharing things just in the hope of getting more upvotes is not. The rule of thumb to follow is "If somebody else had posted this, would I still really want to share it?" If the answer is yes, then go ahead. More guidelines on self-promotion.
My problem is that to can be ambiguous. (This applies to some other keywords as well, but I think it's especially pertinent to words like to). Their meaning in the language normally only follows one of the many meanings in English
While idly surfing the namespace I noticed an odd looking object called Ellipsis, it does not seem to be or do anything special, but it's a globally available builtin.
After a search I found that it is used in some obscure variant of the slicing syntax by Numpy and Scipy... but almost nothing e...
I don't do this anymore but in a previous revision of yuno, inputs would be eval'd and lists with an ellipsis object at the end would be converted to a sequence (infinite length list) by the interpreter if possible
My instinct with JS is to make its type system more cursed lol
Overloading is a sorely needed feature that could be a lot of fun
How about a .name property of objects, and any two objects with the same name become identical? So a = { name: "x" }; b = { name: "x" }; a.id = 2; b.id // 2
Plus since functions already have a name, that would make any functions with the same name identical, which is "good".
It would ignore scope obviously. This prevents two private methods with the same name from existing, which is good. Confusion is bad.
Mandatory and unintended code reuse for the win.
How about any object with a .run method is a function, and for any function f, f.run = f? That makes it so that you can make any variable callable as a function.
Maybe add some underscores, those make everything better
remake of the chatiquette; it doesn't change much in terms of the actual content, mostly just reordered some things, mentioned the current list of ROs+mods if people need someone to handle things, and renamed PPCG to CGCC because that's clearly very important :P
opinions on using this vs just keeping what we have?
the old project is owned by Doorknob so it is still possible to update it but i don't want to bother him since a) he isn't in chat and b) he seems quite busy already
@hyper-neutrino Given some recent history, I'd suggest adding "Don't announce your entrance/exit to the room; The sidebar shows when users join and leave, and doing so is unnecessary noise"
I would say no. If nothing is happening there's no need to announce your entrance/exit, but if there's an ongoing conversation that you're in, announcing your departure is probably fine / even good practice, and in terms of announcing your arrival, I'd say... keep it minimal/reasonable.
The puppet keeps awarding you rep (bounties, upvotes, etc.) until, at some point, it is removed, and you lose however much rep you gained, but all at once
Modify to Increment: Javascript Edition (WIP)
answer-chaining javascript
Your task is to insert bytes/characters into the previous answer such that it outputs the next number in sequence, spelled out in English, as its return value. The first answer must output 'one'.
Example
Answer 1
_=>'one'
...
My Generic Review Tool should result in considerably less strain on both the device running it and the servers, so I think I'll lower the update interval to 40s.
my only declined flag is from flagging a post that someone posted that was blatantly off-topic; it was a mod flag because they'd posted three blatantly off-topic / irrelevant posts, including one being a repost of their answer that several people already said wasn't an answer
so i flagged them for polluting the site which a mod declined ¯\_(ツ)_/¯
i would've just marked it helpful and ignored it unless the user posted anything more
We currently have four tags about up/down-voting:
down-votes
up-votes
voting
votes
There's an argument to be made for keeping down-votes separate since there's a bit of stuff about downvoting culture specifically which isn't necessarily related to the voting mechanism as a whole. However, brows...
Modify to Increment: Javascript Edition (WIP)
answer-chaining javascript
Your task is to insert bytes/characters into the previous answer such that it outputs the next number in sequence, spelled out in English, as its return value. The first answer must output 'one'.
Example
Answer 1
_=>'one'
...
