# Sandbox for Proposed Challenges

This "sandbox" is a place where Code Golf users can get feedback on prospective challenges they wish to post to main. This is useful because writing a clear and fully specified challenge on your first try can be difficult, and there is a much better chance of your challenge being well received if you post it in the sandbox first.

Sandbox FAQ

## Posting

Write your challenge just as you would when actually posting it, though you can optionally add a title at the top. You may also add some notes about specific things you would like to clarify before posting it. Other users will help you improve your challenge by rating and discussing it.

When you think your challenge is ready for the public, go ahead and post it, and replace the post here with a link to the challenge and delete the sandbox post.

## Discussion

The purpose of the sandbox is to give and receive feedback on posts. If you want to, feel free to give feedback to any posts you see here. Important things to comment about can include:

• Parts of the challenge you found unclear
• Problems that could make the challenge uninteresting or unfit for the site

You don't need any qualifications to review sandbox posts. The target audience of most of these challenges is code golfers like you, so anything you find unclear will probably be unclear to others.

If you think one of your posts requires more feedback, but it's been ignored, you can ask for feedback in The Nineteenth Byte. It's not only allowed, but highly recommended! Be patient and try not to nag people though, you might have to ask multiple times.

It is recommended to leave your posts in the sandbox for at least several days, and until it receives upvotes and any feedback has been addressed.

## Other

Search the sandbox / Browse your pending proposals

The sandbox works best if you sort posts by active.

To add an inline tag to a proposal, use shortcut link syntax with a prefix: [tag:king-of-the-hill]. To search for posts with a certain tag, include the name in quotes: "king-of-the-hill".

Get the Sandbox Viewer to view the sandbox more easily!

# Convert JSON object of directories to list of paths

• What's the scoring criterion? Does the shortest code win? If so, then please specify the code-golf tag. Mar 15 at 14:02
• May we expect the input to be non-empty? Mar 15 at 19:24
• Can we take the input in other formats (I'm thinking in favour of languages without native JSON support)? E.g. as a ragged named list, list of nested tuples etc? Mar 15 at 19:28
• JSON typically doesn't have order defined. And some standard doesn't allow duplicate keys while some others support duplicate keys. For example {"a":{"b":{}},"a":{"c":{}}} could be a valid JSON in some standard.
– tsh
Mar 16 at 3:08
• @pajonk Shouldn't JSON be string? And I believe most language should support string at least any languages that support ragged list.
– tsh
Mar 16 at 3:09
• @tsh, yeah, I was thinking about built-in JSON parsing to other structure. Some languages may have advantage from it, while other will be stuck to string-parsing. But that was just a suggestion for OP to decide. Mar 16 at 5:26
• @pajonk The input is non-empty, in the sense that there will always be a JSON object, but it could be {}. In this case, the output must be empty or a newline. Mar 16 at 8:56
• @pajonk I was thinking to allow as input either a string, a dictionary, or a list of tuples, each tuple contains the name and the value (which is a list of tuples). What you think? I'm open to suggestions. Mar 16 at 9:04
• @tsh Since I would allow dictionary as a valid input format, and since the JSON object represents a directory structure, the input won't have duplicate keys. Mar 16 at 9:06
• I would allow the use of basic JSON parsing libraries in languages that don't have built in JSON support Mar 16 at 9:08
• @MatteoC. Yes, I think allowing reasonable equivalents to JSON seems fine. Also, with this relaxed rule I would not allow "basic JSON parsing libraries" as it may be ambiguous what to qualify as "basic". Mar 16 at 12:22
• I strongly discourage too narrow output format (at least a list of directories should be acceptable IMO). Mar 19 at 20:58

# Infinite Candle Sequence

• I'm not sure if this is really two challenges (generate sequence, draw colours). Please let me know! Apr 28 at 3:52
• This really does seem like two challenges. I recommend just requiring answers to output the number sequence, as it does make the challenge more accessible to languages that do not have any form of graphical output. That being said, if it is going to be a purely sequence challenge: Is floating point precision error allowed? Or does the whole decimal number have to be outputted? Or are we outputting as a list of pairs (numerator, denominator)? I also recommend including the first 100 terms or so of this sequence in the challenge body somewhere, as to remove any ambiguity. Apr 28 at 3:59
• If it's going to be graphical output: How should the colors be displayed (square, circle, any shape that you choose, etc.)? Apr 28 at 4:02
• If it's graphical output, you should provide hex codes or screenshots of the first few colors in the sequence. Apr 28 at 8:22
• Thanks for the feedback. I think I'll reduce this to just outputting the sequence. I'll add more info as well. Apr 28 at 22:06
• I've edited this down to a stub now that it's been posted to save space May 4 at 23:12

# Binary Palindromes

Take an input of a positive integer and determine if the binary representation of that number is palindromic. Except for 0 (which is not in the scope of this problem), all binary palindromes are odd, so you do not have to worry about leading/trailing zeroes.

OEIS Sequence: https://oeis.org/A006995

This is code-golf, so shortest answer in bytes wins.

## Test Cases

1 -> True (1)
4 -> False (100)
85 -> True (1010101)
131 -> False (10000011)

• I personally think this question is trivial, but I may be wrong so I didn't downvote it. May 10 at 14:23
• take this as an answer, str(bin(n))[2:][::-1]==str(bin(n))[2:] May 10 at 14:26
• Very closely related: codegolf.stackexchange.com/questions/216929/based-palindromes. May even be considered duplicate by some? Better wait for input from other users and/or ask in chat. May 10 at 19:30
• Didn't see that one because I searched specifically for binary. Will ask in chat. May 10 at 19:32

# LOOONG TEEEXT

## Definition of long text

Long text usually shows emphasis, for instance, loooooool or yaaaaaaaaaay. Usually the vowel is replicated many times. In this challenge we require:

• At least 3 times, which means yaaay and yaaaay are allowed, but yay and yaay are not.

• Consistent, which means that shoes can turn out be shoooeees or shooooeeees but not shoooeeees or shooooeees. Of course, it seems that no one would do that, however, this is to reinforce the next law.

• Undoubling, which means beeping turns out to be beeepiiing or beeeepiiiing but not beeeeeepiiing or beeeeeeeepiiiing. This is not the case for long text, but such makes this challenge non-trivial.

• Thus, the long text might turn out shorter than the original text, that is, aaaaa can turn out to be aaa.

### Input

Your input will be a sentence, that is, you may not assume there are only words. We do not guarantine all will be english words, so look out for theeeeeeeeese.

### Output

The long text for the input.

## Test cases

We assume you repeat 3 times.

The fox yawns...  => Theee fooox yaaawns...

Everything is good!!!!!  => Eeeveeerythiiing iiis goood!!!!!

Note the treatment of capital letters.

Only the letters from a, e, i, o, and u are vowels, case insensitive.

New contributor
Number Basher is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
• How do you determine what a vowel is? I assume the question cares about letters not phonemes, so is it aeiou? You test cases imply that y and w, which are sometimes vowel letters, are not treated as vowel however is this a universal?
– Wheat Wizard Mod
May 12 at 8:52
• Oops, guess I should specify that... May 12 at 9:16

# Whyte Notation Translator

( tags : code-golf, kolmogorov-complexity ? )

Whyte Notation is a classification method mainly for steam locomotive, that classifies by wheel arrangement. On a steam locomotive ( we're only focusing on non articulated locomotives here ), the wheels are generally disposed like this : you have a specific number of leading wheels, then a specific number of driver wheels, and then a specific number of trailing wheels. On the top of that, each different wheel arrangement has its own name.

For example, look at this machine :

It has 2 leading wheels ( 1 on each sides ), 8 driving wheels ( 4 on each sides ) and 2 trailing wheels ( 1 on each sides )

Its Whyte Notation would be 2-8-2, and its name associated with it is "Mikado". Based on the Whyte Notation, we can create a visual arrangement that can be represented by a string, with the o character as a small wheel ( leading wheel if in front of the driver wheels, else trailing ), and a caps O for the driver wheels

Taking the previous locomotive as an example, its visual arrangement would be this : oOOOOo, with one small o on the front ( the leading wheels ), 4 caps O in the middle ( the driving wheels ), and one small o at the end ( the trailing wheels )

Here is the conversion table that we'll use to base the code on ( the table of entries that will have to be supported by your code ) :

    Input    |   Output
-------------+----------
oO           | Planet
oOo          | Jenny Lind
oOO          | Porter
oOOo         | Columbian
ooO          | Jervis
ooOoo        | Huntington
oooO         | Cramton
OO           | Four-coupled
OOo          | Olomana
OOoo         | Forney
ooOO         | American
ooOOo        | Atlantic
ooOOoo       | Jubilee
oOOO         | Mogul
oOOOo        | Prairie
ooOOO        | Ten-wheeler
ooOOOo       | Pacific
ooOOOoo      | Hudson
OOOO         | Eight-coupled
oOOOO        | Consolidation
oOOOOoo      | Berkshire
ooOOOO       | Mastodon
ooOOOOo      | Mountain
ooOOOOoo     | Northern
oooOOOOooo   | Turbine
OOOOO        | Ten-coupled
OOOOOo       | Union
oOOOOO       | Decapod
ooOOOOOo     | Overland
oOOOOOo      | Santa Fe
oOOOOOOoo    | Texas
ooOOOOOOo    | Union Pacific
ooOOOOOOOoo  | AA20


### First program / function : from arrangement to name

The first function / program will be taking as input a string that exists in the table given previously, and will output the associated name ( for example, oOOOOo will return "Mikado" ).

For the input, the only inputs you have to support are the one in the table previously given. Anything else that isn't in the table leads to undefined behavior.

For the output, the string has to be the exact name, with the exception of case, which can be whatever you want. Trailing spaces are fine too.

Examples of acceptable output : Mikado, mikado, MIKADO , mIkAdO, Ten-wheeler

Examples of not acceptable output : Mi Ka Do,  Mikado, Tenwheeler, Ten_wheeler, Ten wheeler

### Second program / function : the opposite

This program of function will do the opposite of the first program, meaning that when given a name, it will print / return / output the string representing the wheel arrangement of the locomotive.

As input, it will take whatever name existing in the "Output" part of the previously given table. Shall the name not exist, it leads to undefined behavior

As output, it will give the exact string that represents the wheel arrangement, no flexibility allowed. So for example, Mikado as input must return oOOOOo.

## Global constraints

Both of the programs have to be able to take as input the other program's output, and func2(func1(wheel_arrangement_string)) has to be equal to wheel_arrangement_string. Same goes the other way, with func1(funct2(wheel_arrangement_name)) that has to be equal to wheel_arrangement_name.

Aside from that, standard I/O rules apply, and default loopholes are forbidden

## Scoring rules

Your score will simply be the sum of each program / function code sizes. Each functions need to support all the entries listed in the table previously given

• I think the scoring is sufficiently punishing to answers missing any cases that none will be able to make use of that in interesting ways. yesterday
• @RadvylfPrograms That's true, i guess i could change that to a multiplication instead. How about S = codesizefunc1 * (1+u) + codesizefunc2 * (1+v) ? Or maybe using the square root on u and v ? yesterday
• Those might work too, but then you run into the risk of people optimizing the combination of code size and cases handled, and getting something boring like x=>"AA20". I think it'd be better to just use the sum of the code sizes as the score. Since it seems like parsing the os into indices into a list is probably going to be how most solutions work, and that's the interesting part of the challenge (since the outputs can't really be compressed), you might even consider allowing a third program that provides the list of names, that's weighted to count for less. yesterday
• @RadvylfPrograms What would be the purpose of the third program and the reduced weight of it ? 2 hours ago

# Reverse hex cipher

Characters in strings are sometimes represented as their ASCII hexadecimal codes. Printable characters have two hex digits in their representation. Swapping those digits leads to another character, which will be our output.

The table of relevant character codes can be found on Wikipedia.

## Details

1. Take a string as input.
2. For each character:
1. Find corresponding hex value of ASCII code.
2. Swap (reverse) the hex digits.
3. Output the new string.

• To make thinks easier, let's consider only characters "reversible" within standard printable ASCII range - that is codepoints (in hex): 22-27,32-37,42-47,52-57,62-67,72-77 or characters: "#$%&'234567BCDEFGRSTUVWbcdefgrstuvw. • Input and output should be made as strings or closest equivalent in your language of choice. • You may assume the input is non-empty. • This is , the usual rules apply. ## Test cases bcd <-> &6F 234 <-> #3C screw <-> 76'Vw debug <-> FV&Wv BEEF <->$TTd
7W66V77 <-> success
"#$%&'234567BCDEFGRSTUVWbcdefgrstuvw <-> "2BRbr#3CScs$4DTdt%5EUeu&6FVfv'7GWgw


# The only differences that matter

Write two programs (or functions) A and B in the same version of the same programming language. They also should be called in the same way, meaning you can't write one program and one function. Each should accept an integer n and output the term n of a different integer sequence on OEIS.

You should reveal a substring of each of A and B. Call them PA and PB. If one instance of PA is replaced by PB from A, it should become B. That means every byte except the reveal part in A and B should be exactly the same. You also reveal the lengths of A and B, and the two OEIS sequences. You don't reveal the programming language you use.

Your answer is cracked if a robber finds two programs A' and B' that also print the elements in the two integer sequences respectively, where A' is no longer than A, and A' with one instance of PA replaced by PB is also B'. They don't have to be the same with your original A and B. And they don't have to be in the same programming language as yours, as long as they are in the same programming language themselves.

If your answer isn't cracked 7 days after you post the answer, you can reveal your language and the original A and B and mark the answer safe, and it will be immune to future crack. Your answer can still be cracked if you don't do it.

Your score is max(len(A)+len(PA)*5, len(B)+len(PB)*5). The safe answer posted before a certain date with the minimum score wins.

For example, if your two programs are The first program and The second program, you can reveal first and second. Your score is 18 + 6*5 = 48. And a robber can crack your answer by <<first>> <<second>> if they work. But you can also reveal first pro and second pro to prevent this crack.

# <length of PA> / <length of A> bytes, <length of PB> / <length of B> bytes, score <score>, <open / safe / cracked>

Part of program A (outputing [<OEIS number>](<OEIS link>)):

<code of PA>

Part of program B (outputing [<OEIS number>](<OEIS link>)):

<code of PB>

<any other explanations>


(To do.)

• Do robbers have to produce the same program, or any program? Oct 28, 2016 at 14:47
• There are two tricky edge cases around character encodings which the question needs to address. 1. It talks about substrings of A and B, saying that every byte except the revealed ones must be the same. If A and B differ in one Unicode codepoint, such that in UTF-8 they differ in only one byte but it's part of a three-byte sequence, can I post just that one byte as PA/PB or must I post the three-byte sequence? (I.e. are the substrings operating on the bytes or on the codepoints?) Oct 28, 2016 at 20:57
• 2. If my program is in APL using an 8-bit encoding, do robbers answering in a language other than APL have to have the same bytes in the part of their file corresponding to PA/PB or the same Unicode codepoints? Oct 28, 2016 at 20:57
• @NathanMerrill Any program. Oct 28, 2016 at 21:05
• @PeterTaylor I'm considering requiring every program to be in printable ASCII (and tabs and newlines), as some special characters effectively banned many languages. But I'm not sure about newlines, which have the \r problem. Oct 28, 2016 at 21:09
• Maybe I'll just say \r\n is counted one byte in this challenge, and is interchangeable with \n. But the programs in one submission must use only \n or only \r\n. Oct 28, 2016 at 21:13
• An example would make this easier to understand,
– xnor
Oct 29, 2016 at 6:08
• I'm skeptical about having the programming language be a free variable. If a cop writes an answer using a verbose language, a robber can comment out all the visible parts and stuff a terse language answer into the cracks. Oct 29, 2016 at 11:24
• @feersum But that's the whole point of all the requirements. If you comment out all the visible parts, both your programs usually should output the same thing. But I realized it's easy to have some workarounds in languages such as Befunge. I may try to find a way to ban them, or just abandon this post. Oct 31, 2016 at 0:59

# Translation Polyglot

Your task is to write a program which runs in two distinct programming languages to translate text. Input should be translated between each language i.e. running your code in Code Language A translates from language 1 to 2, while running your code in Code Language B translates from language 2 to 1.

Rules:

• Code Languages must be distinct, two versions of the same language are disallowed
• Your code may be a full program or function
• Your code must take one string (or nearest equivalent) as input. Input may be user input, function arguments, or other reasonable form
• Output may be a function return, output to STDOUT, or other reasonable form. I do not care about trailing newlines or spaces
• Your code may translate from/to any language on the official language list on Wikipedia. List the languages in your answer
• To accomplish your goal, you may use prebuilt language tanslation dictionaries such as the ones found here.
• If you read your dictionary as an external file, only the code to read in the file (f = open("dictionary.txt", 'r') in Python) counts towards your byte count. If your dictionary is hardcoded in, only count the bytes required to make it syntatically valid code (s="word1_in_english word1_in_french ..." would be 4 (s="")). Essentially, do not include the dictionary as part of your submissions byte count.
• The dictionary you use must have been created before this post (including sandbox time). You may not modifiy the dictionary in any way.
• Any built-in translation tools are disallowed. Built-in dictionaries are ok, but whatever code used to import them into your code must be included in the byte count

This is code golf, so shortest answer in bytes wins.

• wait... Are you actually asking for machine translation? Seems very difficult. Haven't you ever seen bad translator? If it actually is machine translation, this won't work, because of the different resolution of the languages (like converting a jpg to a png and expecting the same quality back) Nov 1, 2016 at 4:11
• It's really just value lookup. I'm not asking people to to make their own dictionary, just use a pre-built and accept whatever it translates Nov 1, 2016 at 13:45
• But that doesn't really satisfy Language A produces output O from input I, while running in Language B produces output I from input O. Nov 1, 2016 at 22:04
• Ah, now I see the source of confusion. Updated text to require basic translation, not symmetric translation Nov 2, 2016 at 11:53
• Also I don't think translation is objective enough for code golf... Nov 3, 2016 at 5:30

# What in the heck just happened?

I want you to write a program that will bleep out the H-word, regardless of where it occurs, whether it is inside of another word or a stand-alone word, whether capitalized or not.

## Input and Output

The inputs and outputs of your program may be any of the following: an array of characters, a string, or any other standard data structure which does the job. However, the output must match the case of the input.

## Samples:

In the format of Input: Output
A Shell gas station : A Sheck gas station
Hell is a very bad place to be. : Heck is a very bad place to be.
Ella fell and Nelly dug a well. : Ella fell and Nelly dug a well.
Chellsea Thell bought shells. : Checksea Theck bought shecks.


Standard loopholes apply, and the entry submitted by [insert date here] with the lowest number of bytes as defined by the Meta will win.

• I can't say for sure, as I don't have an exact reference, but I'm pretty sure a simple find and replace challenge has been done before. Feb 13, 2017 at 0:19
• "Hell" and "heck" are both "H-words", so you need to be clearer. Also, I feel like this is a duplicate. Though these are milder swear words, I think someone did one with swear words in general and it got deleted. If you're going to make a find/replace challenge, it's simple enough to make it about something else. Feb 13, 2017 at 0:19
• Ah, I see. So, are you saying I should change what's being replaced or what my idea is? Feb 14, 2017 at 0:50

# Prove the Undecideability of the Halting Problem

Either:

Create a program that, when given an input, no single program (which receives your source and your input) can determine if your program terminates, or

Create a function that, when given an input, no single program (which receives your source and your input) can determine if your function returns.

Your score is the byte count of your program plus the byte count of your input (or of the shortest input in the set of input that solves this problem).

Lowest score wins.

//I would love some input on my wording.

• Can I make a request to an external URL until I get a 404?
– user58826
May 17, 2017 at 18:21
• @programmer5000 can an external program determine whether your program will halt? For example, by pinging that URL themselves? May 17, 2017 at 18:24
• Oh. Could I make a program that stops when it finds 5 points that prove the Happy Ending Problem wrong?
– user58826
May 17, 2017 at 18:29
• @programmer5000 if your program stops with a given input, and another program can predict that it will stop with that input, your program does not match specs. No input is accepted input, but it is very unlikely that an undecidable program can come from no input AFAIK. May 17, 2017 at 18:32
• @programmer5000 from the Wikipedia page it seems like that problem is already solved, so that program will terminate, so another program could predict that. Could be wrong though. May 17, 2017 at 18:33
• Um. eval. It's one byte long in GolfScript. May 17, 2017 at 21:35
• @PeterTaylor you need to provide an input that is undecidable, and that counts towards your score. May 17, 2017 at 21:38
• I don't think this is how the halting problem works... May 17, 2017 at 23:50
• @DestructibleLemon You may be right; Wikipedia says a general algorithm to solve the halting problem for all possible program-input pairs cannot exist. Do I need to require two inputs? This answer seems to contradict Wikipedia though. May 18, 2017 at 0:10
• hmmm, you definitely could do this (make it an interpreter) but I'm not sure how much you have to do to make this work... as in what the simplest program would be May 18, 2017 at 0:17
• @StephenS It doesn't require 2 inputs, it requires a pair (program, input). May 18, 2017 at 1:07
• It's the problem which is undecidable, not the instances. If you want to ask for a program which cannot be proven to halt or not halt, you have to specify the axiom system which can be used for the proof. See e.g. codegolf.stackexchange.com/q/79470/194 , codegolf.stackexchange.com/q/79620/194 May 18, 2017 at 6:19

# Bike saddle drawn through a fractal

Based on the Mandelbrot image in every language, and on the observation the 3rd layer (0 indexed) always looks like a bike saddle, I had a little bit different challenge:

• Language must be capable of graphical output or drawing charts (saving files disallowed)
• Render a window or control that is resizable by mouse action. As example, it can be a typical GUI Window with the typical frame that allows resizing
• After resizing the GUI element, the fractal should be updated according to the new pixel space
• The fractal coordinates range from approximately -2-2i to 2+2i
• The pixels outside of the 3rd layer (0 indexed) of Mandelbrot set should have one color; the ones inside 3rd and inner layers should have another. The only two colors used should be clearly distinguishable
• At least 99 iterations
• ASCII art not allowed

Winning conditions:
Shortest version (size in bytes) for each language will get a mention in this post, ordered by size.
No answer will ever be 'accepted' with the button.

• @Mark Jeronimus: credits to you. May 27, 2017 at 8:48

Here's a thing: Let's do the bignum bakeoff again.

Because why not.

### What to do

Write a program in less than 256 characters that outputs the biggest number you can.
Yep, that's it. Biggest return value wins.

We'll run the program on a VM with infinite memory. (How do we do this?)

### Rules

• 256 chars max, excluding whitespace
• Different leagues for each language
• Output however you want
• No explicitly printing numbers until your loop runs out. Print the number you generate directly. {1}
• Program must terminate
• No implementation-dependent shenanigans.
• Implementation-independent shenanigans is encouraged.
• ints are infinite.
• Program must return the same number every time
• Submission must include the approximate return value in any suitable googological notation.
• Whitespace is space, tab, newline, formfeed, and return
• BrainF***: Whitespace is all non-[]+-<> characters

{1} Allowed ways to return: printf("%d", num); return num;, etc.
Banned ways to return: for(;num>0;num--)printf("99999");, etc.

### This is not a dupe of...

This because you can put any characters you want, not just non-digits; because we're hard-limiting the characters.

### Suggested rules

• No floats: float double long double, etc
• No strings or chars
• No bitfeilds
• No looking at Command-line args

Next year's contest will be named after this year's winner, for no particular reason.

http://djm.cc/bignum-rules-posted.txt

### Sandbox

• How do you even test these programs?
• What other rules should we have?
• You don't actually explain the rules of the challenge, we would have to go to that link to find out what we are supposed to do. Aside from that, I think this has a lot of problems with your typing restrictions if these are not limited to C, but limiting it to C wouldn't really fit the spirit of the site. I think you may want to rethink how you want to approach this question. May 29, 2017 at 16:43
• @FryAmTheEggman "Typing restrictions"? (Added proper instructions) May 29, 2017 at 16:45
• Your post doesn't describe how people win. Is it by the largest possible number? Anyway, the problems are things like not counting whitespace, which can easily result in degenerate answers, as well as things like I/O streams and whatnot. All of your extra rules seem entirely based around C with no regard for other languages, which will not go well. May 29, 2017 at 16:48
• In answer to "Because why not": because it will be closed as a dupe. May 29, 2017 at 17:59
• Here's a couple of rules I would consider. 1. Program must generate the same result every time (e.g. not based on timer, probability, or the like). 2. Submissions should include, if not the exact resulting number, at least a best estimate, in scientific notation if need be. May 30, 2017 at 18:32
• Scientific notation? People will post answers that far, far exceed that. In fact, Mathematica, 22: Fold[Power,2~Range~9999] It's 2^3^4^...^9999. That's not being represented anytime soon. May 31, 2017 at 3:31
• This is a duplicate, and is also going to come down a lot to whether or not you allow programs that exceed the computational capacity of any existing computer. (If you require programs to work on a physical computer, the best they can possibly do is to use the entirety of memory as a counter and print out 9s over and over again. If you don't, the answers can easily be large enough that you need to use notation invented specifically for describing the number, because all other notations are not enough.)
– user62131
May 31, 2017 at 22:40
• If your code can simulate a Turing machine, it becomes hard to judge who the winner is, and whether an answer is valid at all. Jun 1, 2017 at 20:35
• Re your latest edit: you're wrong. The question it's a dupe of also has a hard limit to the number of characters; in fact it's a harder one, but the best answers could be copied with slight tweaking to take advantage of the extra space. And the digit restriction turned out not to be a serious problem: the winning answer would gain extremely little from being able to use digits. Jun 2, 2017 at 9:07

# Do nothing

Write a program which terminates normally (not in an error), producing no output on the standard output stream (or the language's closest equivalent), nor on the standard error stream, regardless of what content is present on the standard input stream. (Note that this is intentionally overriding the normal I/O defaults; this is a challenge entirely about input/output handling.)

Additionally, your program may not have any other side effects (e.g. writing files, changing persistent state), unless they're an unavoidable consequence of running a program on the operating system you're using (e.g. on Linux, it's OK to change the "next process ID number to be assigned" value inside the kernel, because that happens whenever you run a program).

Finally, to avoid numerous uninteresting 0-byte (or boilerplate-plus-0-byte) solutions, you may not use a language in which the shortest program that does nothing (i.e. complies with the above specification) is also the shortest (or tied for the shortest) program which runs without error (but possibly reacts to input or produces output). In other words, you can't use a language unless doing nothing is more verbose than doing something.

## Clarifications

• Intentionally exiting the program early is permitted. If you do exit the program manually, on a system that uses exit codes, you may do so with any exit code.
• Crashing the program is not permitted, even if it (for some reason) exits with a "success" code after the crash.
• "No output" means 0 bytes of output, not even a trailing newline.
• Likewise, your program must be able to handle any finite sequence of bytes on the standard input stream, even if it isn't, say, made of characters in the current encoding (but rather of arbitrary octets). You do not need to handle infinite input, though (e.g. your program won't be connected to /dev/zero or the like).

## Victory condition

As a challenge, shorter is better, measured in bytes. (Remember that if you need to run the program in an unusual way, that incurs a byte penalty, under standard PPCG rules.)

Because languages which are particularly suited for this task (such as Perl and Python) are excluded by the rules, there's not much point in talking about the best answer cross-language; rather, the aim is to find the best answer you can in the language which you submit in. (Historically, on this sort of challenge, answers that are more unusual, interesting, or better-explained have tended to get more votes.)

## Sandbox questions

Is this too trivial? We were discussing it in chat as a joke, and realised that it's actually possibly more interesting than it sounds. I'm fairly sure the spec's correct (although would definitely appreciate knowing if something's wrong here!), but would appreciate feedback on how much people would hate me if I posted it to main.

• you can't use a language unless doing nothing is more verbose than doing something.you can't use a program unless your program is more verbose than any other program which does something. You must provide a shorter program which does something to prove your solutions validity.
Jun 8, 2017 at 1:03
• @Adám: If you did that, people would just add a comment byte or two to create a program of the shortest possible length that was longer than a program that did something. That isn't particularly interesting.
– user62131
Jun 8, 2017 at 1:21

# Draw an XBox

Here's an X:

\  /
\/
/\
/  \


And here's a Box:

+----+
|    |
|    |
|    |
|    |
+----+


So, for an XBox, just draw an X in a Box:

+----+
|\  /|
| \/ |
| /\ |
|/  \|
+----+


Your input will be a number (in any standard way) that will represent the size of the box. To output the above box, this could be the number of -/|\s (4), or the number of lines/columns (6), or even the intercept of the second diagonal (5) would be acceptable. (Don't ask me to accept the base256 encoding of the output though, as that's one of the many banned standard loopholes.)

Your program or function should then output (in any standard way) the XBox of the given size. If the \/s cross in the same character, place an X (as per Draw a big slash X). For example, here's an XBox three sizes larger than the one above:

+-------+
|\     /|
| \   / |
|  \ /  |
|   X   |
|  / \  |
| /   \ |
|/     \|
+-------+


This is , so the shortest program wins!

• in some obvious way unclear/subjective Jun 9, 2017 at 16:35
• @MDXF 4 examples weren't sufficient?
– Neil
Jun 9, 2017 at 17:04
• I'm just warning you that it could get closed for being too broad due to that statement. Jun 9, 2017 at 17:05
• I agree with @MDXF Jun 9, 2017 at 18:03
• @BetaDecay That's all very well, but I'm unclear as to what you want.
– Neil
Jun 9, 2017 at 19:15
• Just a basic explanation of how scaling works. Some examples would suffice Jun 9, 2017 at 21:32
– Neil
Jun 10, 2017 at 0:42
• @MDXF Here's my problem. I just tried implementing this in Charcoal, and came up with Try it online!. As it turns out, to produce those example XBoxes I actually need sizes of 7 and 10, but I didn't want to penalise that choice of input just because I hadn't predicted that particular scaling.
– Neil
Jun 10, 2017 at 13:42
• @BetaDecay If you still have any further input it would be appreciated.
– Neil
Jun 12, 2017 at 12:06
• Related Jun 15, 2017 at 11:57
• @KevinCruijssen Ugh, I even have an answer on that question... I guess the use of specific characters doesn't really sufficiently distinguish this one.
– Neil
Jun 15, 2017 at 12:42
• @Neil Well, using /+x\ instead of just * does make it a bit trickier, but it's indeed a bit too similar imho. Jun 15, 2017 at 13:11

# Plan and Chain a route through OEIS

Your Task is to reach so many OEIS sequences you could make with chaining your last sequence with a operation to a new sequence.

You must avoid last sequence minus last sequence plus first sequence or something similar that your new sequence is based on the first sequence except to make the second sequence.

Your starting OEIS sequence is in every case https://oeis.org/A001477

Given as Input an positive Integer and a Letter that matches [A-Z] or [a-Z]

# PHP, 171 bytes

for($a=0;$a<=$argv[1];$a++)$r[]=[$a,$b=$a&1,$c=$a+!$b,$d=(($c-!$b)/2^0)+$b,$A[$b]=$e=$d*$c,$f=$e+$A[!$b],$g=$a?$g*sqrt($f):1,$h=$g%2];echo$r[$argv[1]][ord($argv[2])%32-1];  Try it online! The example gives back the n value of a OEIS sequence for the following letters. A letter greater h is for this example a invalid input • a https://oeis.org/A001477 numbers $a Valid first sequence

• b https://oeis.org/A000035 mod 2
$b=$a&1 Valid use the variable in the sequence before

• c https://oeis.org/A109613 odd numbers
$c=$a+!$b Valid Can use sequences before • d https://oeis.org/A110654 a(n) = floor(n/2) + n mod 2 $d=(($c-!$b)/2^0)+$b Valid an invalid example is $d=(($a/2)^0)+$b cause it not use the sequence before

• e https://oeis.org/A000217 triangular
$A[$b]=$e=$d*$c Valid you can create help variables • f https://oeis.org/A000290 square $f=$e+$A[!$b] Valid use a help variabale and the variable of the sequence before. $f=$A[!$b]+$A[!$b] Invalid causes it makes the same value but use indirectly the variable of the sequence before

• g https://oeis.org/A000142 factorial $g=$a?$g*sqrt($f):1 Valid cause your condition is not always the case that it have no relationship to the sequence before.

• h https://oeis.org/A019590 Fermat's Last Theorem $h=$g%2 Valid but now we have the problem to find the next sequence

Could You make a full alphabet? My alphabet ends with the letter h

• I'm rather confused as to what is being asked here. It might be helpful to state how one can get from one sequence to another.
– Wheat Wizard Mod
Jun 10, 2017 at 20:47
• @WheatWizard I could understand you. The problem is at the moment to make rules that avoid that a trivial solution exits. There are too many sequences in OEIS. The way from every sequence to the next should not end in a simple addition or multiplication. But evrything else should be allowed to get more creative solutions Jun 10, 2017 at 20:56
• (1) The first sentence says that the aim is to build the longest chain possible, but the scoring mechanism rewards average code length per element in the chain rather than number of chains. I would think it most likely as it stands that the winner would be a chain of length 1 or at most 2. (2) If you delete everything from the header Example to the end, do you think that the question still makes sense? If not (and I don't think it does), it needs a lot of work. (3) What do the two values in the input mean? Why is the second one a letter rather than a number? Jun 10, 2017 at 21:10
• (4) I'm not sure how feasible it is to write objective rules which forbid "trivial" expressions. (5) It is not clear how to interpret the rule about the 32nd term where either it is not known or the sequence is finite and shorter than 32 terms. Jun 10, 2017 at 21:12
• @PeterTaylor (1) Think you that popularity Contest is a better winning criteria? (2+3) to limit the chaining length to 26. The goal is to show relationsships between two or more sequences. (4+5) Yes it is not easy and I can drop it if I switch to popularity Contest Jun 10, 2017 at 21:26
• @WheatWizard I allow now trivial solutions Jun 10, 2017 at 21:53
• I'm not clear on the purpose of the inputs if we're just supposed to hard code our way from one sequence to the next​. Replacing your PHP example with more generic, more verbose pseudo-code might help. Jun 11, 2017 at 0:16
• @programmer5000 exists a limit of correct tags? Jun 11, 2017 at 11:39
• @Shaggy See it as restriction for ways to code. You must have a chaining to the sequence before. So far I know any working code is a pseudocode Jun 11, 2017 at 11:48

Your program or function must, given a string in any standard input format, output an infinite stream of delimiter-separated strings where each string is determined from the previous by a braiding algorithm. The program starts with printing the input string.

The algorithm is described as follows: Infinitely alternate between

(1) splitting the string into three substrings then swapping the first two substrings and flattening.

and

(2) splitting the string into three substrings then swapping the last two substrings and flattening.

starting with (1).

The three substrings should be of non-increasing length with the maximum length no more than 1 greater than the minimum length of the three substrings. (This means that when the length of the given string is a multiple of three, the three substrings should be the same length. When the length of the given string is one more than a multiple of three, the first substring should be one character longer than each of the last two substrings. When the length of the given string is two more than a multiple of three, the first and second substrings should each be one character longer than the last substring.)

### Example

Let the input be "abcdefg". Let the delimiter be a newline.

Then the program would first print "abcdefg".

It applies (1) which splits the string into ["abc","de","fg"] and swaps the first two elements, reaching ["de","abc","fg"]. It flattens to get "deabcfg" which it prints and uses for the next step.

The program applies (2) to "deabcfg" to split into ["dea","bc","fg"] and swaps into ["dea","fg","bc"], flattening to reach "deafgbc".

The program applies (1) to "deafgbc" and the process repeats ad infinitum.

Then the output would be the newline-separated

abcdefg
deabcfg
deafgbc
fgdeabc
fgdbcea
bcfgdea
bcfeagd
eabcfgd
eabgdcf
gdeabcf
gdecfab
cfgdeab
cfgabde
abcfgde
abcdefg
deabcfg
deafgbc
fgdeabc
fgdbcea
bcfgdea
bcfeagd
eabcfgd
eabgdcf
gdeabcf
gdecfab
cfgdeab
cfgabde
abcfgde
abcdefg
[...]


### Specifications

• Note that the string should not be split at the beginning and then only swapped later. The string should be split on each and every iteration
• The delimiter between lines could be whichever character is convenient. You may assume it does not appear in the input string.
• The string input shall be at least three characters
• The input consists solely of printable characters (0x20-0x7F)
• Of course, standard loopholes are forbidden.

### I/O

• The input and output should be taken in standard I/O methods.
• The input and output should be taken as string, list of characters, or equivalent.
• The output should be output continuously, which means you may assume infinite memory.

### Test cases

For the test cases, we will assume that the delimiter is a newline. Just the portion before the endless stream is repeats is shown.

input
--
output
-----
abcdefg
--
abcdefg
deabcfg
deafgbc
fgdeabc
fgdbcea
bcfgdea
bcfeagd
eabcfgd
eabgdcf
gdeabcf
gdecfab
cfgdeab
cfgabde
abcfgde
-----
abc
--
abc
bac
bca
cba
cab
acb
-----
abcdefgh
--
abcdefgh
defabcgh
defghabc
ghabcdef
bcdghaef
bcdefgha
efgbcdha
efghabcd
habefgcd
habcdefg
cdehabfg
cdefghab
fghcdeab
fghabcde
abcfghde
abcdefgh
-----
Braid
--
Braid
aiBrd
aidBr
dBair
dBrai
raidB
idraB
idBra
Brida
-----
Cycle
--
Cycle
clCye
cleCy
eCcly
eCycl
yceCl
ycleC
leycC
leCyc
Cylec
-----
--
anaO Cda!
da!anaO C
da!O Cana
O Cda!ana
-----
A man, a plan, a canal - panama!
--
A man, a plan, a canal - panama!
an, a canalA man, a pl - panama!
an, a canal - panama!A man, a pl
- panama!Aan, a canal man, a pl
- panama!A man, a plan, a canal
man, a pla - panama!An, a canal
man, a plan, a canal - panama!A
n, a canal  man, a pla- panama!A
n, a canal - panama!A man, a pla
- panama!A n, a canal man, a pla
- panama!A man, a plan, a canal
man, a plan- panama!A , a canal
man, a plan, a canal - panama!A
, a canal -man, a plan panama!A
, a canal - panama!A man, a plan
panama!A m, a canal -an, a plan
panama!A man, a plan, a canal -
an, a plan, panama!A m a canal -
an, a plan, a canal - panama!A m
a canal - an, a plan,panama!A m
a canal - panama!A man, a plan,
panama!A ma a canal - n, a plan,
panama!A man, a plan, a canal -
n, a plan, panama!A maa canal -
n, a plan, a canal - panama!A ma
a canal - pn, a plan, anama!A ma
a canal - panama!A man, a plan,
anama!A mana canal - p, a plan,
anama!A man, a plan, a canal - p
, a plan, aanama!A man canal - p
, a plan, a canal - panama!A man
canal - pa, a plan, anama!A man
canal - panama!A man, a plan, a
nama!A man, canal - pa a plan, a
nama!A man, a plan, a canal - pa
a plan, a nama!A man,canal - pa
a plan, a canal - panama!A man,
canal - pan a plan, a ama!A man,
canal - panama!A man, a plan, a
ama!A man, canal - pana plan, a
ama!A man, a plan, a canal - pan
a plan, a cama!A man, anal - pan
a plan, a canal - panama!A man,
anal - panaa plan, a cma!A man,
anal - panama!A man, a plan, a c
ma!A man, aanal - pana plan, a c
ma!A man, a plan, a canal - pana
plan, a cama!A man, anal - pana
plan, a canal - panama!A man, a
nal - panam plan, a caa!A man, a
nal - panama!A man, a plan, a ca
a!A man, a nal - panamplan, a ca
a!A man, a plan, a canal - panam
plan, a cana!A man, a al - panam
plan, a canal - panama!A man, a
al - panamaplan, a can!A man, a
al - panama!A man, a plan, a can
!A man, a pal - panamalan, a can
!A man, a plan, a canal - panama
lan, a cana!A man, a pl - panama
lan, a canal - panama!A man, a p
l - panama!lan, a canaA man, a p
l - panama!A man, a plan, a cana
A man, a pll - panama!an, a cana


# Rock Paper Scissors, but it's a big, custom tournament

We all know "Rock, Paper, Scissors", and it's pretty variated.

A world tournament is held every year, and it's dang popular.

However, the contestants are able to bring their own ways of play to the plate, and they play with them.

# The challenge:

Create a program that, by process of elimination through RPS, determines the winner of the tournament.

# The tournament rules:

• No slackers. (Let the amount of players be an integer equally divisible by 2. [In other words, an even number.])

• You can bring 2 of either of the 4 variants:

None: Play regular RPS.

RPSLV: Play "Rock, Paper, Scissors, Lizard, Spock" (play diagram shown here).

Best out of three: Play 3 rounds; if by round 2, a player wins the round and has two points, they auto win. Else, winner of the next round wins.

Double RPS: Play with four hands (two hands used by each player).

• You cannot bring two of the same variant.

• In order to use a variant, the two players must have the same type of variant. If there are no matching variants, the gameplay is automatically None.

• However, if there are more than one variant matches, a game of mode None will be played. The winner of the game mentioned decides what mode they play for the match they will play to see who goes to the next round.

• In the case of a tie, replay until a win occurs (for all modes)

• There can be only one winner.

# The coding rules:

• All choices must be randomized (no strategies, to make this simple.).

• No standard loopholes.

• Give an explanation as much as you can. (If possible, include a "Try it out online" sample.)

# Sample Input/Output:

You must make a table variable with all the player numbers, from 1 to n, with two variants for each player.

n = the amount of players you intend to enter.

Example Input:

Player # | Var 1 | Var 2
1        | RSPLV | None
2        | None  | x2 RPS
3        | x2 RPS| Boo3
4        | Boo3  | x2 RPS
...      |...    | ...


Make a func() that:

1: Checks the variants of the next two availible players on the list, starting at player 1, then does the second to third last rules depending on what happens.

2: Makes the pair engage in battle, gameplay depending on the chosen variant.

3: Finally, boot the loser off the game and add the winner to the next list (round). (The "boot the loser" part isn't that required, but I recommend so as to not make the program add a player to the next table.)

Output (uses table from input):

 Round 1:
1 vs. 2 // None, since the None variant matches both of them
["Rock"/*1*/,"Scissors"/*2*/]
1 wins

3 vs. 4 // They have more than one match, so they fight for who decides
["P"/*3*/,"S"/*4*/]
4 wins, and chooses Best out of 3
Match 1:
["P"/*3*/,"R"/*4*/] // 1(3) - 0(4)

Match 2:
["P"/*3*/,"S"/*4*/] // 1(3) - 1(4)

Match 3:
["P"/*3*/,"R"/*4*/] // 2(3) - 1(4)
3 wins

Round 2:
1 vs. 4 //No matches, defaults to None
["R"/*1*/,"R"/*4*/] // No-one wins
["R"/*1*/,"S"/*4*/]
1 wins the tournament


# Misc. requirements (some optional):

A {!} means it is required.

• {!} Print each match, and who wins.

• {!} Print the tournament winner.

• {!} The number of players must be flexible.

• Print the table for each round.

# Scenarios:

None:

a vs. b //Either they have no matches, or they have both None matches
["R"/*a*/,"S"/*b*/]
a wins


RPSLV (will make this one quick):

a vs. b //RPSLV chosen
["V"/*a*/,"L"/*b*/]
b wins


Best out of Three:

Scenario 1: (a tie occurs at match 2)

a vs. b //Boo3 chosen
Match 1:
["P"/*a*/,"S"/*b*/] // 0(a) - 1(b)

Match 2:
["P"/*a*/,"P"/*b*/] // tie
["P"/*a*/,"S"/*b*/] // 1(a) - 1(b)

Match 3:
["R"/*a*/,"S"/*4*/] // 2(a) - 1(b)
a wins


Scenario 2: (a player has two points by the end of match 2)

a vs. b //Boo3 chosen
Match 1:
["P"/*a*/,"S"/*b*/] // 0(a) - 1(b)

Match 2:
["S"/*a*/,"P"/*b*/] // 0(a) - 2(b)
b automatically wins


Double RPS:

a vs. b //x2 RPS chosen
[("R", "P")/*a*/, ("S", "S")/*b*/] // lock
[("P", "P")/*a*/, ("S", "S")/*b*/]
b wins


# For sandbox use only (won't be included in real question)

I don't know if this kind of problem is suitable for code golf, it could be a programming puzzle, I'm not sure. Go ahead in the comments and tell me what mode it should be, and if I should improve it. (Also, sorry for the mix of Python lists and C++ comments, if it confuses you.) A ** means the choice is random.

• Hi and welcome to PPCG, and thanks for using the sandbox! I had a hard time following what you intended from this challenge. The rules are rather disorganised with many points early on not making sense until later. For example, you say: "No slackers. (Let p be a number equally divisible by 2.)" before it is clear that you intend for us to implement a single elimination tournament. I had no idea what "p" was supposed to mean, or why this should matter. I'd recommend trying to explain this to someone verbally, perhaps, to try to organise your thoughts better. Good luck! Jul 15, 2017 at 21:50
• Ah, thanks. I will edit the problem. Jul 15, 2017 at 22:03
• I'm not quite sure what we're supposed to implement. The controller for the tournament and what else? Do we also implement the players, so that we're simulating the entire thing? Or do we have to provide some kind of API for the players? In the first case, how does "The winner decides what mode they play" work? Jul 16, 2017 at 7:14
• Again, any multi-choice is random. Jul 16, 2017 at 19:29

# Quick! Tell me all the numbers from 1 to 100,000! fastest-codenumbers

Your task is to write a program or function that, when run, output all the numbers from 1 to 100 thousand as quickly as possible to STDOUT. It's that simple. All answers are tested on an HP Compaq nx9420 with an Intel Core Duo @ 1.83 GHz and 3 gigs of RAM using the time command.

Of course, standard loopholes are strictly forbidden.
This is , so may the fastest code win and the best programmer prosper...

• Have you tried running an example to see if the times are variable enough to be meaningful? As-is, this is going to be strongly dependent upon how fast the code can do I/O, which makes the challenge pretty uninteresting, IMO. Jul 19, 2017 at 18:16
• @AdmBorkBork Might be interesting Jul 19, 2017 at 21:12
• As far as I can tell, this takes less than a tenth of a second, which means submissions will probably be differentiated solely by noise on your computer. Jul 20, 2017 at 2:37
• upvoted, though I think the differenciation is really difficult, unless you test it on a raspberry PI (for example) having ONLY the program and its compiler installed. Jul 20, 2017 at 13:36
• @FryAmTheEggman How could I improve on that? Jul 20, 2017 at 23:38
• @V.Courtois I do have a Pi, and I think I will use that (it has Raspbian installed). Jul 20, 2017 at 23:39
• The time is still so small even a basic operating system will have to much noise in process creation, etc, for this to work out. You need to make what we are computing substantially more complicated for this to be reasonable. Jul 21, 2017 at 0:10
• @FryAmTheEggman K Jul 21, 2017 at 1:20
• @ckjbgames good then :) Jul 21, 2017 at 5:26

# Is it cat-urday?

Caturday is one of the oldest memes out there. For this challenge you need to write a program that outputs the input, but only on Saturday.

## The catch:

You can acquire the date via UNIX timestamp, or as a formatted date string (local or UTC). However, you can not:

• use day of the week information in a date string
• directly acquire the day of the week of a date by some other means
• use Date or Calendar functions, beyond one to simply give you the current date
• use any external resources (files, Internet)

Don't forget leap years!

Does this question work as is? Should I make anything clearer?

• This is a "do X without Y" challenges, and those have been done to death. Jul 22, 2017 at 20:28

# What's that character? (Part 1) code-golf

Recently I ran a command on my laptop that returned a bunch of characters - some printable, some non-printable. I'm having trouble figuring out what those characters are, so I could use some help. Unfortunately, I'm running low on disk space, so you'll have to write me the shortest program you can that I can run.

# Challenge

Given a list of ASCII characters, return their names as written on www.asciitable.com, my go-to site for looking up character points.

### Input

You may take a string, a list of characters, or a list of ASCII code points (e.g. 'a' -> 97).

You may optionally take the length of the string/list as well. Note that for C, you must take this parameter, since the string could contain NUL bytes, so strlen won't work here.

### Output

Output is flexible as usual; you may print or return from a function as you see fit. You should output a list of strings.

### The Table

0 NUL
1 SOH
2 STX
3 ETX
4 EOT
5 ENQ
6 ACK
7 BEL
8 BS
9 TAB
10 LF
11 VT
12 FF
13 CR
14 SO
15 SI
16 DLE
17 DC1
18 DC2
19 DC3
20 DC4
21 NAK
22 SYN
23 ETB
24 CAN
25 EM
26 SUB
27 ESC
28 FS
29 GS
30 RS
31 US
32 Space
33 !
34 "
35 #
36 $37 % 38 & 39 ' 40 ( 41 ) 42 * 43 + 44 , 45 - 46 . 47 / 48 0 49 1 50 2 51 3 52 4 53 5 54 6 55 7 56 8 57 9 58 : 59 ; 60 63 ? 64 @ 65 A 66 B 67 C 68 D 69 E 70 F 71 G 72 H 73 I 74 J 75 K 76 L 77 M 78 N 79 O 80 P 81 Q 82 R 83 S 84 T 85 U 86 V 87 W 88 X 89 Y 90 Z 91 [ 92 \ 93 ] 94 ^ 95 _ 96  97 a 98 b 99 c 100 d 101 e 102 f 103 g 104 h 105 i 106 j 107 k 108 l 109 m 110 n 111 o 112 p 113 q 114 r 115 s 116 t 117 u 118 v 119 w 120 x 121 y 122 z 123 { 124 | 125 } 126 ~ 127 DEL  # Test Cases [0, 97, 7, 22] -> [NUL, a, BEL, SYN]  More to come... # Meta • Would it be more interesting to use the UTF-8 names for the printable characters (0x20 - 0x7E), and the ASCII names for the control characters? • hand copy the table from the website please dont. Try a Google search: theasciicode.com.ar/ascii-codes.txt Jul 23, 2017 at 22:39 • @StepHen good call, thanks Jul 23, 2017 at 23:24 • Downvoter: I would much like your feedback rather than just your vote Jul 24, 2017 at 1:39 • IMO just have take a letter and output the code. Since that part is boilerplate str.chars.map( real program ). Also for ASCII char names NUL is it ok is we output them in lower case? e.g. nul (obviously ascii letters would have fixed case) Jul 24, 2017 at 1:42 # Lennyface parser and selector ## Your mission Create, in the language of your choice, a program that outputs a randomly selected lennyface (artistic minifigures, see this) from an input - a string composed of numbers and lennyfaces. You will have to : first, parse this input; second, extract a probability mass function f from the parsed input; third, select and output a lennyface respecting f. Read the rules for more details. ## Rules • Input : A string with lennyfaces and numbers (positive AND negative integers), separated by newlines. You may take input by STDIN or function parameter for example. • Output (STDOUT for example) : the randomly-selected lennyface, as a string. • The input creates a probability mass function f. If l is a lennyface, then f(l)=(sum of all numbers since the previous lennyface)/x where x is obtained afterwards by summing each of those numerators. @Sandbox : is it clear enough? • If (sum of all numbers since the previous lennyface) is equal to zero or negative, you must do as if the numerator is equal to 1 in f's definition. • A line with a number contains only this number ; same for a line with a lennyface. So you can assume there will never be a number in a lennyface. • If there is nothing on a line (two newlines in a row), you must consider it as a lennyface. • You must consider that the last line of the string is directly before its first line. See Test 1 for an example. • You can assume there will be at least 1 lennyface in the list; it cannot be composed just by numbers (don't forget that an empty line is a lennyface too). ## Example Given this input list : ( ͡° ͜ʖ ͡°) 2 ¯\_ツ_/¯ 34 -4 8 └[⸟‿⸟]┘ 1  You must have 1/42 chances of outputting ( ͡° ͜ʖ ͡°), 2/42 chances of outputting ¯\_ツ_/¯, 38/42 chances of outputting └[⸟‿⸟]┘ and 1/42 chances of outputting nothing (line 7). ## Test cases Test 1 (⌐■_■) 3  Must output (⌐■_■) with 3/3 chances. Test 2 ʢ◉ᴥ◉ʡ  Must output ʢ◉ᴥ◉ʡ with 1/1 chance. Test 3 0 \(ᗝ)/  Must output \(ᗝ)/ with 1/1 chance. Test 4 ( ͡° ͜ʖ ͡°) 2 ¯\_ツ_/¯ 34 4 ☞  ͜ʖ  ☞ 0  Must output ( ͡° ͜ʖ ͡°) with 1/42 chance, ¯\_ツ_/¯ with 1/21 chance, ☞  ͜ʖ  ☞ with 19/21 chances and nothing with 1/42 chance. Test 5 1 ( ͡° ͜ʖ ͡°)  Must output ( ͡° ͜ʖ ͡°) with 1/4 chance and nothing with 3/4 chance, since there are 3 empty lines. Test 6 42 -1 ( ͡° ͜ʖ ͡°)  Must output nothing with 43/44 chance and ( ͡° ͜ʖ ͡°) with 1/44 chance. @Sandbox : should I add test cases? This is , so shortest code in bytes wins. Standard loopholes apply. Note : Please do not be discouraged if the parsing is difficult to handle in your language, or if testing is hard because of randomness. Your solution might be very interesting algorithmically, not obviously in terms of golfing. Just please explain in your answer why it works. Moreover, this is the first code-golf I create, so please let me know if something is not appropriate or if I should give more details on a point. And overall, if you downvote, explain me why so I can improve it. • Yours tests seems a bit contraditory. The number is the chance of the next face (line), so what's the point of the empty line in the example / test 4? By the same logic, the test1 should have a 3/4 of outputting nothing? What is the point of the 0 in the test 4? – Rod Jul 3, 2017 at 14:03 • Why is the chance of outputting ( ͡° ͜ʖ ͡°) 1/42 and not 0 ? (since there are no numbers above it) – Dada Jul 3, 2017 at 14:04 • Sorry ! I forgot to copy paste the fact that the minimal chance is 1! Jul 3, 2017 at 14:05 • Also, a common thing to do on challenges involving randomness, and therefore, hard to test, is to ask people to provide a mandatory explanation, or at least ask them to show why it works. – Dada Jul 3, 2017 at 14:05 • @Dada thanks. I note this. Jul 3, 2017 at 14:06 • @Rod the empty line is a lennyface, as said here : If there is nothing on a line, you must consider it as a lennyface. Jul 3, 2017 at 14:08 • @V.Courtois I meant and empty line without a preceding number – Rod Jul 3, 2017 at 14:09 • As I said, the minimum is one (sorry again for forgetting it). Jul 3, 2017 at 14:10 • If only positive integers are to be expected, you should write it. Otherwise, give some details and examples about what you consider "numbers". – Dada Jul 3, 2017 at 14:12 • @Dada editing. In fact I said the minimum is 1, but you can have things like 2,-1,-3,17 and then your lennyface ; that means the probability is 15/ total. Jul 3, 2017 at 14:14 • @V.Courtois just a small suggestion, to make the "list as circle" more explicit you could change the value to something else than 0 or 1, this way it would not overlap the "missing number" rule – Rod Jul 3, 2017 at 14:15 • @Rod does it? Sorry if I'm not getting what you are saying, but the list is always a circle, meaning if your list is 2,3,( ͡° ͜ʖ ͡°),4,5,☞  ͜ʖ  ☞,6, you have 6+2+3 chance of getting ( ͡° ͜ʖ ͡°) and 4+5 chance of getting ☞  ͜ʖ  ☞. Jul 3, 2017 at 14:18 • thanks for editing @musicman523 Jul 4, 2017 at 7:21 • KISS. This is far more complicated than common sense would require. Deliberately overcomplicating things to make it "more difficult" is a guaranteed method to make a bad question. Jul 4, 2017 at 7:32 • The challenge has two parts as far as I can tell. a) Create a probability mass function from an input by parsing b) sample from the probability mass function. Part a) needs to be rewritten as it is at best ambiguous and at worst just incorrect. – user9206 Jul 5, 2017 at 7:50 # Golf Cubically code code-challengefgitw Your task is to optimize Cubically source code using one or more optimizations in this post. How this challenge works: • You will choose one or more optimizations below and write a program (in the language of your choice) that performs those optimizations on a Cubically program. • Your program will take a Cubically program as input using any allowed input methods, and output a Cubically program using any allowed output methods. • The first answer to successfully perform all optimizations wins! # Optimizations ### 1. Face turn arguments Before a face turn is performed, the interpreter calculates turns = turns mod 4. So R5 would be equivalent to R1 which is equivalent to R, R7 is equivalent to R3 which is equivalent to R', etc. Also note that R11111 is equivalent to R5, and R22 is equivalent to nothing at all. Performing this optimization will mean evaluating all arguments to an R, L, U, D, M, E, or S command and shortening them as much as possible. Test cases: Relevant code -> Optimization R11 -> R2 R1 -> R L33 -> L2 U22 -> D222 -> D2 M11111 -> M E00001 -> E S9 -> S  ### 2. Repeated face turn When multiple calls to the same face turn command are present right next to each other, they can clearly be golfed. For example, R2R1 is equivalent to R3. UUU is equivalent to U3. F2F2F2F2 is equivalent F8. Test cases: Relevant code -> optimization R2R2R2 -> R6 (R2 if you also choose optimization 1) LLL -> L3 UU -> UU or U2 D3D2D1 -> D6 (D2 if you also choose optimization 1)  ### 3. "Set notepad to" commands There are some commands that, instead of adding to/subtracting from/multiplying by/dividing by the notepad, just assign to it. Here are all such commands: _^=<>⊕«»·|:  When called with multiple arguments, since each argument calls the command separately, only the final argument is relevant. So =123 is equivalent to =3, _00000 is equivalent to _0, and :12345678987654321 is equivalent to 1. Test cases: Relevant code -> Optimization _333 -> _3 =12321 -> =1 +54321 -> +54321 :55 -> :5 /55 -> /55  ### 4. Repeated non-face-turn commands When multiple face turn commands are present right by each other, their arguments can simply be added together. Commands do not act this way. While R2 calls R with 2, =2 calls = with the face sum of the front face (face index 2). To perform this optimization, when multiple commands outside of RLUDFBMES appear next to each other, simply remove the duplicated commands without removing the arguments. Relevant code -> Optimization _1_1_1_1 -> _1111 (_1 if you also choose optimization 3) %11%22%33 -> %112233 (%3 if you also choose optimization 3) +12345+67+8 -> +12345678  ### 5. Nonexistent commands Go check out the Cubically commands page and you'll see that there are plenty of characters that are not commands. For example, there are no commands that are lowercase letters. To perform this optimization, remove all nonexistent commands and their arguments from the Cubically source. If the commands also have arguments, you must remove the arguments so that they are not passed to the previous command. Test cases: Relevant code -> Optimization moo cow moo -> moo2cow2moo -> misteR2 FOO -> R2F FEAR ME. -> ERME u1U2u3U4u5U6 -> U2U4U6 (nothing if you also choose optimization 1, U12 if you also choose optimization 2)  ### 6. Non-implicit commands There are lots of implicit commands in Cubically (RLUDFBMES()$~&E!), but there are plenty that need to be called with arguments. So %%%% is equivalent to nothing at all while %%2%% is equivalent to %2.

Test cases:

Relevant code -> Optimization
%%%%          ->
          -> 
++2++2++2     -> +2+2+2                 (+222 if you also choose optimization 4)
+++>--<-      -> Not Brainf**k, sorry!  (:P)


# Sandbox

• Clarification on R123: That's the same as R6 and R2, not R3, right? Digits are summed, there are multidigit numbers? That would be better to specify Aug 17, 2017 at 20:13
• A few things: first, I can't find the tag "fgitw", is there a typo? Second, does optimization 1 require handling F and B as well, or just the currently listed ones? Third, in optimization 3 most of the listed commands seem invalid because the notepad is used in calculation and then overwritten with the output; for example =11 is not the same as =1 in most circumstances. In fact, I think only _: are valid. Fourth, is the winning answer one which performs all optimizations in a single program, or one which contains a separate program for each optimization? Aug 18, 2017 at 18:03

# Hungry for Apples?

This challenge is simple, given an integer 0 <= n or 0 < n, output an ASCII-apple with that many bites taken out of it.

No bites (0):

         //
.-.:|.-.
.'   ''   '.
;          ;
:            :
:            :
:            :
:          ;
'.        :
'-_.._-'


Bite 1:

         //
.-.:|.-.
.'   ''   '.
;          ;
'-.         :
}         :
.-'         :
:          ;
'.        :
'-_.._-'


Bite 2:

         //
.-.:|.-.
.'   ''   '.
'-.        ;
}         :
}         :
}         :
.-'        ;
'.        :
'-_.._-'


Bite 3:

         //
.-.:|.-.
.'   ''   '.
'-.        ;
}      .-'
}      {
}      '-.
.-'        ;
'.        :
'-_.._-'


Bite 4:

         //
.-.:|.-.
.'   ''   '.
'-.      .-'
}      {
}      {
}      {
.-'      '.
'.        :
'-_.._-'


Bite 5:

         //
.-.:|.-.
.'   ''   '.
'-.      .-'
}".    {
} }    {
} }    {
.-'"     '.
'.        :
'-_.._-'


Bite 6:

         //
.-.:|.-.
.'   ''   '.
'-.      .-'
}"~".  {
} } }  {
} } }  {
.-'"~"   '.
'.        :
'-_.._-'


Bite 7:

         //
.-.:|.-.
.'   ''   '.
'-.      .-'
}"~"~".{
} } } }{
} } } }{
.-'"~"~" '.
'.        :
'-_.._-'


Bite >7:

[empty output]


# Rules

• You may have trailing spaces, make it consistent though.
• You may have exactly 1 trailing newline.
• You are NOT doing an animation here, you are taking in n and outputting an apple.
• You may error on integers less than 0, as the spec provides n > 0.
• You must have empty output (no error) on n > 7/8.
• You threw out the core; you didn't error the core into non-existence.
• I feel this would be better if there was some more symmetry in the 5, 6, and 7 bytes so that people could possibly make better compression. Aug 4, 2017 at 18:26
• @AdmBorkBork better? Aug 22, 2017 at 21:26
• Yes, much better. Aug 23, 2017 at 12:33

# Proper Kerning

Kerning is the adjustment of spacing between pairs of letters in order to obtain an aesthetic result. When kerning is applied automatically by a program (typically whatever editor you're using), it is said to be automatic. There are two types of automatic kerning. The one used in this challenge is metric kerning. With metric kerning, the amount of space between pairs of letters is dictated by the kerning tables found in the font file.

Given a TrueType font file, output the kerning values for each mapping in the kerning table for ASCII characters 48 - 122 inclusive.

## Example

calibri.ttf

l="A" r="C" v="-15"
l="A" r="G" v="-15"
l="A" r="J" v="23"
l="A" r="O" v="-23"
l="A" r="Q" v="-23"
l="A" r="T" v="-160"
l="A" r="U" v="-32"
l="A" r="V" v="-89"
l="A" r="W" v="-80"
l="A" r="Y" v="-150"
l="A" r="t" v="-52"
l="A" r="v" v="-38"
l="A" r="y" v="-41"
l="A" r="?" v="-68"
l="B" r="A" v="-20"
l="B" r="T" v="-48"
l="B" r="V" v="-25"
l="B" r="W" v="-24"
l="B" r="X" v="-44"
l="B" r="Y" v="-57"
l="B" r="Z" v="-20"
l="B" r="f" v="-20"
l="B" r="t" v="-20"
l="B" r="v" v="-20"
l="B" r="x" v="-15"
l="B" r="y" v="-20"
l="C" r="G" v="-18"
l="C" r="J" v="12"
l="C" r="O" v="-18"
l="C" r="Q" v="-18"
l="C" r="T" v="10"
l="D" r="A" v="-30"
l="D" r="J" v="-22"
l="D" r="T" v="-23"
l="D" r="V" v="-24"
l="D" r="W" v="-14"
l="D" r="X" v="-31"
l="D" r="Y" v="-39"
l="D" r="Z" v="-22"
l="E" r="A" v="-22"
l="E" r="C" v="-24"
l="E" r="G" v="-24"
l="E" r="O" v="-32"
l="E" r="Q" v="-32"
l="E" r="S" v="-20"
l="E" r="Z" v="-10"
l="E" r="a" v="-34"
l="E" r="c" v="-28"
l="E" r="d" v="-30"
l="E" r="e" v="-37"
l="E" r="f" v="-64"
l="E" r="o" v="-37"
l="E" r="q" v="-30"
l="E" r="t" v="-24"
l="E" r="v" v="-48"
l="E" r="w" v="-34"
l="E" r="y" v="-48"
l="F" r="A" v="-115"
l="F" r="C" v="-18"
l="F" r="G" v="-18"
l="F" r="J" v="-109"
l="F" r="O" v="-18"
l="F" r="Q" v="-18"
l="F" r="S" v="-29"
l="F" r="X" v="-22"
l="F" r="Z" v="-11"
l="F" r="a" v="-55"
l="F" r="c" v="-28"
l="F" r="d" v="-20"
l="F" r="e" v="-30"
l="F" r="o" v="-28"
l="F" r="q" v="-20"
l="F" r="s" v="-35"
l="G" r="T" v="-10"
l="G" r="V" v="-10"
l="G" r="W" v="-9"
l="G" r="Y" v="-30"
l="G" r="v" v="-29"
l="G" r="w" v="-22"
l="G" r="x" v="-14"
l="G" r="y" v="-30"
l="J" r="A" v="-35"
l="J" r="X" v="-20"
l="K" r="C" v="-78"
l="K" r="G" v="-80"
l="K" r="O" v="-97"
l="K" r="Q" v="-97"
l="K" r="S" v="-18"
l="K" r="U" v="-29"
l="K" r="W" v="-34"
l="K" r="a" v="-34"
l="K" r="c" v="-40"
l="K" r="d" v="-33"
l="K" r="e" v="-37"
l="K" r="f" v="-25"
l="K" r="m" v="-32"
l="K" r="n" v="-32"
l="K" r="o" v="-37"
l="K" r="p" v="-32"
l="K" r="q" v="-33"
l="K" r="r" v="-32"
l="K" r="s" v="-18"
l="K" r="t" v="-38"
l="K" r="u" v="-32"
l="K" r="v" v="-101"
l="K" r="w" v="-95"
l="K" r="y" v="-85"
l="L" r="C" v="-22"
l="L" r="G" v="-47"
l="L" r="J" v="25"
l="L" r="O" v="-45"
l="L" r="Q" v="-45"
l="L" r="T" v="-150"
l="L" r="U" v="-44"
l="L" r="V" v="-147"
l="L" r="W" v="-118"
l="L" r="Y" v="-167"
l="L" r="f" v="-23"
l="L" r="t" v="-38"
l="L" r="v" v="-78"
l="L" r="w" v="-72"
l="L" r="y" v="-79"
l="O" r="A" v="-23"
l="O" r="J" v="-27"
l="O" r="T" v="-55"
l="O" r="V" v="-25"
l="O" r="W" v="-22"
l="O" r="X" v="-64"
l="O" r="Y" v="-55"
l="O" r="Z" v="-38"
l="O" r="x" v="-12"
l="O" r="z" v="-10"
l="P" r="A" v="-151"
l="P" r="J" v="-140"
l="P" r="T" v="-9"
l="P" r="V" v="-10"
l="P" r="X" v="-35"
l="P" r="Y" v="-11"
l="P" r="Z" v="-29"
l="P" r="a" v="-44"
l="P" r="c" v="-43"
l="P" r="d" v="-34"
l="P" r="e" v="-41"
l="P" r="f" v="12"
l="P" r="o" v="-41"
l="P" r="q" v="-34"
l="P" r="s" v="-32"
l="P" r="t" v="12"
l="P" r="y" v="12"
l="Q" r="J" v="41"
l="Q" r="T" v="-47"
l="Q" r="V" v="-25"
l="Q" r="W" v="-12"
l="Q" r="X" v="12"
l="Q" r="Y" v="-46"
l="Q" r="g" v="59"
l="Q" r="j" v="79"
l="Q" r="x" v="31"
l="Q" r=";" v="60"
l="Q" r="]" v="32"
l="R" r="C" v="-18"
l="R" r="G" v="-19"
l="R" r="O" v="-20"
l="R" r="Q" v="-20"
l="R" r="S" v="-27"
l="R" r="T" v="-20"
l="R" r="V" v="-28"
l="R" r="W" v="-18"
l="R" r="Y" v="-30"
l="R" r="e" v="-36"
l="R" r="o" v="-42"
l="R" r="v" v="-26"
l="R" r="w" v="-33"
l="R" r="y" v="-33"
l="S" r="A" v="-15"
l="S" r="J" v="-9"
l="S" r="T" v="-14"
l="S" r="V" v="-14"
l="S" r="W" v="-15"
l="S" r="X" v="-13"
l="S" r="Y" v="-20"
l="S" r="v" v="-23"
l="S" r="w" v="-17"
l="S" r="y" v="-25"
l="T" r="A" v="-160"
l="T" r="C" v="-42"
l="T" r="G" v="-59"
l="T" r="J" v="-65"
l="T" r="O" v="-58"
l="T" r="Q" v="-58"
l="T" r="S" v="-10"
l="T" r="T" v="28"
l="T" r="a" v="-160"
l="T" r="c" v="-177"
l="T" r="d" v="-147"
l="T" r="e" v="-182"
l="T" r="g" v="-151"
l="T" r="m" v="-127"
l="T" r="n" v="-127"
l="T" r="o" v="-182"
l="T" r="p" v="-127"
l="T" r="q" v="-147"
l="T" r="r" v="-127"
l="T" r="s" v="-153"
l="T" r="u" v="-127"
l="T" r="v" v="-92"
l="T" r="w" v="-86"
l="T" r="x" v="-90"
l="T" r="y" v="-93"
l="T" r="z" v="-142"
l="T" r=";" v="-114"
l="T" r=":" v="-134"
l="U" r="A" v="-45"
l="U" r="J" v="-40"
l="V" r="A" v="-96"
l="V" r="C" v="-18"
l="V" r="G" v="-25"
l="V" r="J" v="-80"
l="V" r="O" v="-27"
l="V" r="Q" v="-27"
l="V" r="S" v="-12"
l="V" r="V" v="9"
l="V" r="a" v="-114"
l="V" r="c" v="-103"
l="V" r="d" v="-87"
l="V" r="e" v="-102"
l="V" r="g" v="-100"
l="V" r="m" v="-50"
l="V" r="n" v="-50"
l="V" r="o" v="-86"
l="V" r="p" v="-50"
l="V" r="q" v="-87"
l="V" r="r" v="-50"
l="V" r="s" v="-90"
l="V" r="u" v="-50"
l="V" r="y" v="-35"
l="V" r="z" v="-82"
l="V" r=";" v="-108"
l="V" r=":" v="-73"
l="W" r="A" v="-93"
l="W" r="C" v="-22"
l="W" r="G" v="-22"
l="W" r="J" v="-88"
l="W" r="O" v="-22"
l="W" r="Q" v="-22"
l="W" r="S" v="-10"
l="W" r="X" v="-13"
l="W" r="a" v="-71"
l="W" r="c" v="-78"
l="W" r="d" v="-72"
l="W" r="e" v="-75"
l="W" r="g" v="-54"
l="W" r="m" v="-60"
l="W" r="n" v="-60"
l="W" r="o" v="-86"
l="W" r="p" v="-60"
l="W" r="q" v="-72"
l="W" r="r" v="-60"
l="W" r="s" v="-73"
l="W" r="u" v="-60"
l="W" r="v" v="-34"
l="W" r="y" v="-53"
l="W" r=";" v="-156"
l="X" r="C" v="-57"
l="X" r="G" v="-65"
l="X" r="O" v="-57"
l="X" r="Q" v="-57"
l="X" r="S" v="-20"
l="X" r="d" v="-44"
l="X" r="e" v="-39"
l="X" r="g" v="-9"
l="X" r="o" v="-38"
l="X" r="q" v="-44"
l="X" r="t" v="-31"
l="X" r="u" v="-38"
l="X" r="v" v="-55"
l="X" r="w" v="-49"
l="X" r="y" v="-43"
l="Y" r="A" v="-152"
l="Y" r="C" v="-67"
l="Y" r="G" v="-67"
l="Y" r="J" v="-112"
l="Y" r="O" v="-66"
l="Y" r="Q" v="-66"
l="Y" r="S" v="-17"
l="Y" r="Z" v="-10"
l="Y" r="a" v="-134"
l="Y" r="c" v="-159"
l="Y" r="d" v="-131"
l="Y" r="e" v="-147"
l="Y" r="f" v="-62"
l="Y" r="g" v="-142"
l="Y" r="i" v="-32"
l="Y" r="j" v="-49"
l="Y" r="m" v="-94"
l="Y" r="n" v="-94"
l="Y" r="o" v="-153"
l="Y" r="p" v="-94"
l="Y" r="q" v="-131"
l="Y" r="r" v="-94"
l="Y" r="s" v="-115"
l="Y" r="t" v="-44"
l="Y" r="u" v="-94"
l="Y" r="v" v="-69"
l="Y" r="w" v="-62"
l="Y" r="x" v="-70"
l="Y" r="y" v="-65"
l="Y" r="z" v="-100"
l="Y" r=";" v="-138"
l="Y" r=":" v="-154"
l="Z" r="A" v="-11"
l="Z" r="C" v="-25"
l="Z" r="G" v="-24"
l="Z" r="O" v="-24"
l="Z" r="Q" v="-24"
l="Z" r="W" v="-7"
l="Z" r="Y" v="-7"
l="Z" r="a" v="-10"
l="Z" r="c" v="-12"
l="Z" r="d" v="-18"
l="Z" r="e" v="-31"
l="Z" r="o" v="-29"
l="Z" r="q" v="-18"
l="Z" r="v" v="-45"
l="Z" r="w" v="-38"
l="Z" r="y" v="-37"
l="a" r="f" v="-12"
l="a" r="t" v="-19"
l="a" r="v" v="-34"
l="a" r="w" v="-14"
l="a" r="x" v="-19"
l="a" r="y" v="-38"
l="b" r="f" v="-17"
l="b" r="s" v="-10"
l="b" r="t" v="-9"
l="b" r="v" v="-10"
l="b" r="w" v="-10"
l="b" r="x" v="-41"
l="b" r="y" v="-10"
l="b" r="z" v="-28"
l="c" r="a" v="-17"
l="c" r="o" v="-17"
l="e" r="f" v="-18"
l="e" r="t" v="-11"
l="e" r="v" v="-10"
l="e" r="w" v="-10"
l="e" r="x" v="-31"
l="e" r="y" v="-13"
l="e" r="z" v="-20"
l="f" r="a" v="-40"
l="f" r="c" v="-45"
l="f" r="d" v="-53"
l="f" r="e" v="-51"
l="f" r="f" v="-20"
l="f" r="g" v="-60"
l="f" r="o" v="-43"
l="f" r="q" v="-53"
l="f" r="s" v="-27"
l="f" r="v" v="13"
l="f" r="w" v="6"
l="f" r="y" v="10"
l="f" r="z" v="-20"
l="g" r="a" v="-38"
l="g" r="c" v="-12"
l="g" r="d" v="-19"
l="g" r="e" v="-17"
l="g" r="g" v="19"
l="g" r="o" v="-14"
l="g" r="q" v="-19"
l="g" r="t" v="-31"
l="h" r="f" v="-12"
l="h" r="t" v="-19"
l="h" r="v" v="-34"
l="h" r="w" v="-14"
l="h" r="x" v="-19"
l="h" r="y" v="-38"
l="k" r="a" v="-35"
l="k" r="c" v="-48"
l="k" r="d" v="-56"
l="k" r="e" v="-66"
l="k" r="o" v="-69"
l="k" r="q" v="-56"
l="k" r="s" v="-19"
l="k" r="t" v="-10"
l="k" r="u" v="-26"
l="m" r="f" v="-12"
l="m" r="t" v="-19"
l="m" r="v" v="-34"
l="m" r="w" v="-14"
l="m" r="x" v="-19"
l="m" r="y" v="-38"
l="n" r="f" v="-12"
l="n" r="t" v="-19"
l="n" r="v" v="-34"
l="n" r="w" v="-14"
l="n" r="x" v="-19"
l="n" r="y" v="-38"
l="o" r="v" v="-9"
l="o" r="w" v="-8"
l="o" r="x" v="-40"
l="o" r="y" v="-11"
l="o" r="z" v="-27"
l="p" r="f" v="-17"
l="p" r="s" v="-10"
l="p" r="t" v="-9"
l="p" r="v" v="-10"
l="p" r="w" v="-10"
l="p" r="x" v="-41"
l="p" r="y" v="-10"
l="p" r="z" v="-28"
l="q" r="g" v="10"
l="r" r="a" v="-42"
l="r" r="c" v="-30"
l="r" r="d" v="-28"
l="r" r="e" v="-27"
l="r" r="g" v="-28"
l="r" r="o" v="-33"
l="r" r="q" v="-28"
l="r" r="s" v="-35"
l="r" r="v" v="19"
l="r" r="w" v="11"
l="r" r="y" v="10"
l="s" r="f" v="-19"
l="s" r="t" v="-23"
l="s" r="v" v="-31"
l="s" r="w" v="-10"
l="s" r="x" v="-22"
l="s" r="y" v="-37"
l="s" r="z" v="-18"
l="t" r="a" v="-25"
l="t" r="c" v="-25"
l="t" r="d" v="-23"
l="t" r="e" v="-22"
l="t" r="o" v="-20"
l="t" r="q" v="-23"
l="t" r="t" v="-29"
l="v" r="a" v="-30"
l="v" r="c" v="-25"
l="v" r="d" v="-20"
l="v" r="e" v="-20"
l="v" r="f" v="11"
l="v" r="g" v="-28"
l="v" r="o" v="-19"
l="v" r="q" v="-20"
l="v" r="s" v="-9"
l="v" r="t" v="10"
l="v" r="v" v="12"
l="v" r="w" v="12"
l="v" r="y" v="12"
l="v" r="z" v="-26"
l="w" r="a" v="-23"
l="w" r="c" v="-20"
l="w" r="d" v="-18"
l="w" r="e" v="-18"
l="w" r="f" v="6"
l="w" r="g" v="-18"
l="w" r="o" v="-19"
l="w" r="q" v="-18"
l="w" r="s" v="-18"
l="w" r="t" v="4"
l="w" r="v" v="12"
l="w" r="w" v="8"
l="w" r="y" v="12"
l="w" r="z" v="-17"
l="x" r="a" v="-37"
l="x" r="c" v="-46"
l="x" r="d" v="-44"
l="x" r="e" v="-54"
l="x" r="o" v="-55"
l="x" r="q" v="-44"
l="x" r="s" v="-12"
l="x" r="t" v="6"
l="x" r="u" v="-20"
l="y" r="a" v="-31"
l="y" r="c" v="-26"
l="y" r="d" v="-24"
l="y" r="e" v="-25"
l="y" r="f" v="10"
l="y" r="g" v="-26"
l="y" r="o" v="-24"
l="y" r="q" v="-24"
l="y" r="s" v="-19"
l="y" r="t" v="10"
l="y" r="v" v="12"
l="y" r="w" v="8"
l="y" r="y" v="10"
l="y" r="z" v="-17"
l="z" r="a" v="-34"
l="z" r="c" v="-45"
l="z" r="d" v="-46"
l="z" r="e" v="-46"
l="z" r="f" v="-10"
l="z" r="g" v="-17"
l="z" r="o" v="-45"
l="z" r="q" v="-46"
l="z" r="s" v="-22"
l="z" r="u" v="-10"
l="z" r="v" v="-18"
l="z" r="w" v="-22"
l="z" r="y" v="-18"


## Scoring

This is , so the shortest answer (in bytes) wins.

### Meta

I know this challenge is going to need a lot of work before it's ready for main. Please hold criticisms for now. Helpful ideas and thoughts are welcome.

• I'm not sure that the problem is well defined. There's a reason it's called font hinting: the rendering application is free to take it into account or not, or even to apply more complex logic. E.g. some fonts have multiple sets of font hints for different contexts. There are other complex issues. A font can have Latin and Cyrillic letters and define hints for kerning between pairs of Latin and pairs of Cyrillic but not between Latin and Cyrillic; however, some letters may have identical glyphs, so a judgement on whether the kerning is "correct" might be ambiguous. Then there's antialiasing. May 24, 2017 at 6:15
• @PeterTaylor Good notes. I will likely restrict the character set. I just wanted to start getting ideas down in the sandbox.
– Poke
May 24, 2017 at 6:51
• Very ambiguous. May 25, 2017 at 17:48
• @Mendeleev It's not done yet. I'm aware it's ambiguous.
– Poke
May 26, 2017 at 16:10
• Looking at developer.apple.com/fonts/TrueType-Reference-Manual/RM06/… I can see a number of issues to address. 16- vs 32-bit entries? Should multiple tables be combined or printed separately? All tables or only tables with certain coverage values? Which of the four defined formats need to be supported? Do you have a test case which covers glyph index differing from codepoint? Sep 16, 2017 at 17:28
• @PeterTaylor I have a proof of concept that I wrote (it's the reason I have taken so long to update this) and I'm planning to address all of your questions. Thanks for doing a bit of research to help me out, though :]
– Poke
Sep 16, 2017 at 18:57
• Downvoter, why?
– Poke
Oct 4, 2017 at 21:03

Six Flags over HTTP

Let's say you need to transmit six boolean flags in a URL string. Obviously you could do it with six ones or zeroes, but you want better compression. With a little math you can pack them into two characters using 0-7 octal.

How about mapping all six to a single ASCII character? Here we have a problem: you are not allowed to use , / ? : @ & = + $# or space. Now the range of printable ASCII no longer has 64 valid characters in a row. In Javascript (or another language that can run from a web page, if any), what is the shortest code for a pair of functions to encode and decode this data, between an array of six booleans and a single character? • -1 language restriction, most languages have HTTP libraries so I think any language should be allowed Sep 24, 2017 at 13:11 • This challenge could be improved by rephrasing it to: "Write a bijective function between an array of six booleans and a single printable character excluding the characters ,/?:@&=+$# ". Mentioning that the encoder and decoder should be separate programs/functions would be helpful. Also, may the encoder and decoder share code? Sep 24, 2017 at 22:08

# Count letter frequency

Inspired by question Tweetable hash function challenge, you should take the English dictionary used there and produce a program or function that outputs the the absolute and relative frequency of each character. It is CASE SENSITIVE and the APOSTROPHE is also accountable as a real letter.

Example of a valid output format (but with stupid guessing values):

A      5566    20%
...
Z        60     0.2%
a     27000    30%
...
z       120     0.01%
'       450     3.5%


It is , but no answer will be accepted. Wanna know shortest script for each language.

• -1 (01) Don't rely on another challenge to define yours; include all the information we need in your write-up. (02) Make an effort to come up with some actual test cases - do you honestly expect us to verify our solutions against "stupid guessing values"? Sep 30, 2017 at 0:55

# Is it a perfect loop? test-batterydecision-problem

Your task is to take a GIF or an animated image in any reasonable format as input (including taking the file name of a GIF in the current directory), and output whether it is a "perfect loop" - that is, the frames transition seamlessly from the end to the start, and a human cannot notice where it starts and ends at first glance. Return or print a truthy value if it is a perfect loop, otherwise print or return a falsy value.

## Scoring

Winners will be determined from the percentage of test cases they get correct. In the event of a tie, highest votes wins. You can view test cases at https://ghostbin.com/paste/m3yaw. Show your score against the test cases when you post.

## Input

If you are not taking input in a GIF, please provide a program that will convert a GIF to your desired format.

Images corresponding to a truthy value have been taken from /r/perfectloops and for falsy test cases, /r/almostperfectloops and /r/gifs.

## Restrictions

• Hard coding is not allowed (violates standard loophole 1 and 2).
• You must provide consistent results for the same GIF (no randomness)
• Remember, this is not , so byte count is not needed in your solution. Just post the language name and add the percentage correct when I comment.
• I'm not sure it's as simple as comparing the first to the last frame, if it is we'd have duplicate frames. is this challenge allowing HTTP requests? Oct 17, 2017 at 21:15
• If hashing the inputs is not allowed, then you should clearly define what constitutes a “perfect loop”. It's not good to extrapolate from a handful of test cases where the pass/fail cases are very similar.
– japh
Oct 18, 2017 at 14:31

# Highest code size∕output ratio to generate a large executable section inside an elf file.

Your challenge is to create the shortest code in your language of choice or the tools of your choice (like objcopy) that will create an elf file with a the executable section as large as possible.
I mean that if I extract the.text section of the elf binary, the resulting extracted file should be at least 90% of the elf binary.

# Requirements

• The program should takes the desired section size as input.
• The .text section name needs to corresponds to the executable section.
• The type of the .text section should bePROGBITSand it should contains instructions.
• The elf file should have a .shstrtab section.
• The .text section should be readable and writable.
• The target architecture should be Pnacl or armelv7 or x86_64.
• The elf file should be valid and pass Google nacl’s validation whitelist in order to be loaded (but I don´t care if the sandbox segfault).
If you have no idea about what Google native client is, just create a script that call the patched version of binutils from the nacl_sdk, or make sure the elf file is valid and can be executed on Linux.

Of course, you normally can’t use a compiler because it would takes too much computational years in order to finish.

# Winner

The answer with the highest code size∕program output ratio.

• Why not make scoring output size / code size`? Apr 4, 2017 at 3:49
• Make it a code-challenge Apr 4, 2017 at 3:49
• This is essentially the same challenge as this one, and would be closed as a duplicate. Although it's not exactly the same, some answers to the previous question would require very little modification and answers to this question would also require very little modification to be answers to the other one. Apr 4, 2017 at 8:37
• @Alt-F4 : it was a code challenge. Apr 4, 2017 at 21:52
• @PeterTaylor : they were no answer to the previous question. In order to be closed as a duplicate the target needs to be already answered. You known it was closed an unclear, so please suggest change to make this answer clearer. Apr 4, 2017 at 21:54
• Huh? It's open and has 15 answers. Apr 4, 2017 at 22:09
• @PeterTaylor sorry, I thought to an another question that was closed as unclear and didn’t take time to read your link. In that case NO, the aim is to not use the compiler in order to actually build the file. This normally can’t be done with a compiler or an assembler. Apr 4, 2017 at 22:16
• Can't it? Why not? Dec 16, 2017 at 19:55
• Wait... shortest code that generate any program? Or what? Don't think this is a good idea... Jan 6, 2018 at 12:10