Unless specified otherwise, strings are case-sensitive. More generally, unless specified otherwise, strings are just sequences of characters with no semantics attached to any specific characters.
This should also be the least surprising default for users who are not aware of this post.
I'd also urge challenge authors to think twice before making a ...
Let's keep it.
Though it encompasses a wide variety of challenges, I do think it adds a level of context not readily available with separate tags like number-theory, arithmetic, or what have you.
Consider this (admittedly contrived) scenario. Say a user is thinking, "I'd like to participate in a mathy challenge but I don't have a particular type of math in ...
As the author of ;# and the original challenge, I kind of feel obligated to weigh in here. The semicolon-# tag doesn't really add anything to the site, and as demonstrated by my last attempt, all most variations of the original challenge have been done.*
I see no real point in having a language specific tag for every "Implement this language" ...
Adding emphasis to the quote from the tag wiki:
This challenge involves creating or parsing pictures using text characters as the paint. Typically this uses only 95 printable (from a total of 128) characters defined by the ASCII Standard from 1963.
Without even modifying the wiki it seems that the tag covers art created with larger character sets, or ...
Let's delete the tag once and for all
First of all, as stated in the question:
Challenges involving printing lyrics often all use the same, uninteresting tactics. Having the lyric tag suggests we want more like this.
Most often, the tactics in the answers include converting the lyrics into another base and then decoding it (boring!). In We're no ...
self-referential would be strictly weaker than quine. quine should only be used for tasks involving the actual manipulation of the program's source, which is not required for the challenges linked.
While "Output with the same length as the code" could theoretically be done by using a standard extensible quine to get the source, computing the length of ...
tips should be tagged code-golf or whatever contest type they relate to. This will make it clear that not all tips are necessarily about code golf.
I don't think we need to bother creating a bunch of new tags like king-of-the-hill-tips because we don't get that many tips questions to begin with, so there is not a huge need to be able to subscribe to ...
Retire it but leave it be
As it stands, only 4 challenges bear that tag. It wouldn't be a huge endeavor to retag them. However, the 1p5 tag itself obviously has notable historical significance for our site. Thus I think we should keep the tag around to mark the challenges that were part of this effort, but retire its use for new challenges.
In general, I ...
Funny you should mention it, I thought about this yesterday (not for the first time), and was planning to collect a list of challenges for the retagging today. I'm definitely in favour of this, because these challenges are fairly hard to search for, because the terminology in use may vary a lot ("parenthesis", "bracket", "brace", "matching", "matched", "...
There are two different usages of "code golf" here:
The tag code-golf is applied to challenges which involve competing to produce the shortest valid source code. More details and a list of challenges can be found by clicking on the tag name.
This website, "codegolf.stackexchange.com", has the full name Programming Puzzles & Code Golf. This site has ...
I agree, word should become natural-language. We could either retag the current 26 challenges bearing that tag (not all at once) or make word a synonym of natural-language. I propose we do the latter.
Note: To vote on the proposed synonym, go here.
Those which are fastest-algorithm should obviously be retagged with that. For those which require answers to be in a certain time complexity, I propose creating restricted-time-complexity by analogy with restricted-source. Then time-complexity can be left for the cleanup script to delete.
Let's create a [stateful] tag
I propose a stateful tag which should be generic enough that it isn't limited to self-modification but should encompass the general idea that running the program multiple times will result in different behaviour.
The most important thing that this doesn't include is randomness and time-based behaviour. The behaviour should ...
Lets remove some other language tags too
I have noticed a large number of language based tags that are only attached to one or two questions. Particularly a large number of tags only attached to a tips question. And if we intend to get rid of semicolon-# we should get rid of some other seldom used language-based tags.
The kolmogorov-complexity tag was initially applied only to what you might term pure Kolmogorov complexity questions: those which asked for a constant output. Its scope has expanded over time, and I have also felt that its application to some questions was overbroadening it. However, to limit it to constant-output questions would be to overnarrow it.
Keep them separate
A good number of the matrix challenges are about grids of numbers that do not represent any linear transformation. Conversely, the five linear-algebra challenges you note do not involve matrices, but are about vectorspaces, independence, abstract transformations, etc. Though these are a minority, I think it would not be accurate to tag ...
Winning Criteria/Question Type
Every question should have at least one of these tags.
Please use this search query to find questions without one, and tag with the correct tag if the winning criterion is specified in the question. Currently (Jan. 9, 2021) there are none!
If you think there needs to be a new category, post an answer to the Let's create ...
No, we should not create a flag tag
It's sufficient to tag challenges related to flags as ascii-art, code-golf (if applicable), and kolmogorov-complexity. The context of a flag will be apparent from the title.
All challenges relating to flags will be essentially the same challenge but with a different pattern to mimic.
I think having a tag for this is a good idea. The other solutions are great, but I'm going to throw out another one:
This seems to be the most popular solution, so I went ahead and created this tag. I'm going to slowly edit it into the questions that Martin has linked (to avoid flooding the front-page).
The tag wiki is here. ...
The code-golf tag wiki excerpt says:
Code-golf is a competition to solve a particular problem in the fewest bytes of source code. If you want to score by characters instead of bytes, state this explicitly in the challenge. If source code length is not the primary scoring criterion, consider using another tag instead.
While byte count is a part of your ...
Both derivatives and cousins of chess should be included
It makes sense for other games that are closely related to chess to be included in the chess tag. I propose the following wording for the header of the tag wiki:
This tag is for challenges related to chess or any variation on chess.
The longer description can be edited in the same way. It may be ...