Sandbox for Proposed Challenges

Question

What is the Sandbox?

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

To post to the Sandbox, scroll to the bottom of this page or click on the "Add Proposal" link below, and click "Answer This Question". Click "OK" when it asks if you really want to add another answer. Write your challenge just as you would when actually posting it. 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, replace the post here with a link to the challenge and delete it.

See the Sandbox FAQ for more information on how to use the Sandbox.

The Sandbox works best if you sort posts by "active".

Add Proposal

Search the Sandbox

• Most people include applicable tags in their proposal, so for instance you can search for all king-of-the-hill proposals by merely adding the tag name in quotes to the search query.

Browse your pending proposals

Get the Sandbox Viewer to view the sandbox more easily

To add an inline tag to a proposal use shortcut link syntax with a prefix: [tag:king-of-the-hill]

Answer 1

Move a window around the screen

Your code should open a new window that is at least 100 by 100 pixels in size. Once the window is open you should be able to move the window around the screen using the keyboard. The window should move smoothly but it doesn't matter how fast it moves.

gui code-golf

Answer 2

Output a Random Bit

random internet code-golf

Your task is simple: print either 1 or 0.

Chosen uniformly randomly every time.

No, not your silly pseudorandom nonsense. No system calls. No reading /dev/urandom. The randomness has to be unpredictable (i.e. reliant on chaotic, impossible-to-reasonably-model natural phenomena, and not on some configuration of bits in your computer).

Specifications

• It is OK to query a site such as random.org for your bit.
• Your program only needs to be runnable once per day (i.e. you can assume there is a 24 hour gap between executions). This is to work around the fact that sites like random.org often have rate-limits.

Answer 3

Let's play the too high too - low game!

TL:DR : write a code that plays the too high - too low game

---

Given this pseudo code function for the too high - too low game, write it in your language of choice. This is just to make the challenge work better across all languages. This code won't count in the final score. You may also change the function's name and any of its variable's name too.

function isRight(number, guess):  # where the number is the correct answer and the guess is your code's guess

    if guess < number:            # if the guess is too low
        return 0                  # return 0

    else if guess > number:       # if the guess is too high
        return 2                  # return 2

    else if guess == number:      # if the guess is right
        return 1                  # return 1

    else:                         # if there is an error
        return -1                 # return -1

---

The challenge

Write a code, function, script, etc. that guesses the right number. The range of the "random" number will be between 0 inclusively and 100 exclusively. For the sake of this challenge, the "random" numbers will be the test cases. Note that hard-coding the test cases is banned.

---

Scoring

This is how the score will be counted:

bytes = number of bytes in your code
tries = the sum of all the tries used to guess all the test cases

score = bytes + tries

---

Rules

• Hard-coding the test cases if forbidden.

---

Test cases

[0,2,4,13,19,21,26,33,38,42,48,50,51,56,66,69,74,75,80,89,98,99]

Answer 4

♫ I see a window and I want it painted black ♫

Yes, I know this is a popular mishearing of the lyrics. But instead of a red door, I really do want an (application) window painted black.

Your standalone program should launch an application window at least 400x400 and fill it entirely with black. It doesn't need to be borderless, and it doesn't need to exit gracefully.

Running in a browser is insufficient because there are still elements of the window such as the address-bar and tab-bar that aren't painted black. You must paint the whole window black except for borders added by your window manager.

This is code golf. Standard loopholes apply. Additional challenge is to listen to The Rolling Stones while making your submission.

Here is an un-golfed Java solution:

#compile: javac BlackWindow.java
#run: java BlackWindow
import java.awt.Color;
import java.awt.Frame;

public class BlackWindow{
  public static void main(String[] args){
    Frame frame = new Frame("no colors anymore");
    frame.setsize(400, 400);
    frame.setLocationRelativeTo(null);
    frame.setBackground(Color.Black);
    frame.setvisible(true);
  }
}

Answer 5

Shorter coding in non-golfing language

Copper write a requirement, a sample program in a golfing language, and a required non-golfing language. Rob hack it with the required language, with fewer bytes of code.

I guess it'd be popularity-contest cuz it's sometimes hard to define which is "golfing language". Also is it a duplicate?

Answer 6

(Now I don't know what the name should be)

Intention

I want to create a challenge based on dependent typing, feature that exists in Idris, Coq, Agda and the similiar.

Text

code-golf

You should create a function in dependently typed language (Idris, Coq, Agda, etc) so that:

1. The function will receive a string that denotes format.
2. The format string will have s or n, s means it will receive a string, n means it will receive a number. You can assume that there is no other thing in the string
3. Arguments is received in order. If there is type mismatch, the error must be reported on compile-time.
4. After all arguments is received, the function will return a string, that is list of all passed argument

For example

formatf "sn" "goods" 25
> "goods 25"
formatf "sn" "goods" "bad"
> Type error in compile time
formatf "ak" "Akangka" 25
> You can do anything.
formatf "nnn" 24 25
> Either type error or return a function expecting a number and return string (currying is almost universal in these languages)
formatf "ss" "Akangka" "Martin Ender" "Adám"
> Type error on compile time

This challenge is similiar to printf-style string formatting, the difference that the function in this challenge has to be type safe.

Note that you cannot use build-in function or macro to do this

Discussion

1. What should be the name of this challenge?

Answer 7

Quecho, a quine-like implementation of echo.

Challenge:

Your challenge is to write a quine-like program that takes a string from stdin and gives two outputs: Output A is the input string. Output B is your source code.

Output Formats:

You can send your outputs to stdout, stderr, and/or files. If A and B go to the same output, they must be separated by a newline. Having a newline at the beginning of your source doesn't count. You'd need to print that newline from your source and then another newline to separate A and B.

Examples:

source: print($stdin+"\n"+codeThatGeneratesSource)

input: Hello, World!

Both outputs on stdout:

Hello, World!
print($stdin+"\n"+codeThatGeneratesSource)

Separate Outputs:

stdout: Hello, World!

stderr: print($stdin+"\n"+codeThatGeneratesSource)

Standard loopholes are forbidden.

Submissions should be proper quines except that they produce the additional specified output.

Answer 8

• This is in sandbox to check whether or not to repost the BrainF**k interpreter challenge. The links have been given in credits.
• Should comment handling be required.
• Also any other improvements are welcome

code-golf interpreter

BrainF**k:

BrainF**k is an esoteric programming language designed in the 90s. The reason for its fame is that understanding a program longer than 10 characters in the language is quite hard.

Example program :

>++++++++[<++++++++>-]<++++++++++++++++.[-]

Guess what this does.

---

Commands:

Brainf**k operates on an array of memory cells, also referred to as the tape, each initially set to zero. There is a pointer, initially pointing to the first memory cell.

There are a total of eight commands in BF and these are as follows:

Command       |                              Purpose
  >           |      increment the data pointer (to point to the next cell to the right).
  <           |      decrement the data pointer (to point to the next cell to the left).
  +           |      increment (increase by one) the byte at the data pointer. 
  -           |      decrement (decrease by one) the byte at the data pointer.
  .           |      output the byte at the data pointer
  ,           |      one byte of input, storing its value in the byte at the data pointer.
  [           |      if the byte at the data pointer is zero, then instead of moving the instruction pointer forward to the next command, jump it forward to the command after the matching ] command.
  ]           |      if the byte at the data pointer is nonzero, then instead of moving the instruction pointer forward to the next command, jump it back to the command after the matching [ command.

---

Note :

+ and - operators increment and decrement the bytes at the at the data pointer, note that if the value reaches 255 then upon a + it would become 0.

255 + 1 = 0

Similarly if the value reaches 0 then upon the next - it would become 255.

0 - 1 = 255

---

Input:

You will be given two strings as input:

• The actual BrainF**k code that you are supposed to interpret.
• the program input (that will eventually be emptied) to be interpreted as an array of bytes using each character's ASCII code and will be consumed by the , instruction

Example:

Program : +[,>,]<.
stdin   : 11111 

---

Output:

• the output of the interpreted code, if any was produced by the . instruction.

Example:

For the above mentioned program, the output should be:

output: 1

---

Notes:

• Both program and stdin will be given as strings.
• The output should be a string showing the result after operations.
• Given input will always be valid, with a valid BrainF**k program.
• In order to avoid confusion, note that you do not need to output the word output as well

e.g :

 output : 1

in this your output should only be 1. (asked by @Picard)

Credits:

The question was (more or less) already asked here. This has been reposted since that was 7 years old and was outdated as well.

Meta posts on that:

• Asked by me regarding my repost now..
• Another one, about reposts in general.
• Martin Ender's post about closing old questions in favor of new.

---

Examples:

Program: +[>>>>+++++[-<++>]<[-<++++++++++>]<[-<<->>]<<-[>-<[-]]>+<,]>[>>+>+<<<-]>>>[<<<+>>>-]<<+>[<->[>++++++++++<[->-[>+>>]>[+[-<+>]>+>>]<<<<<]>[-]++++++++[<++++++>-]>[<<+>>-]>[<<+>>-]<<]>]<[->>++++++++[<++++++>-]]<[.[-]<]<
stdin: Hello, World. This is a program for checking eeeeeeee. Well I have plenty of e
output: 14

Program: ++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]>>.>---.+++++++..+++.>>.<-.<.+++.------.--------.>>+.>++.
stdin: 
output: Hello, World

---

Winning-criteria:

This is code-golf, so the shortest code in bytes for each language wins.

Answer 9

Longest reference

Write two code A and B, where len(A)<=1024, running A returns B and running B returns A. Longest B win.

Proper quine rule and no rubbish rule(for code-bowling) apply.

Un-used Code

All code must be used. Meaning the program must fail to always properly complete the task if any individual character (or varying set(s) of characters) is/are removed. Naturally, a subset of the program should not be able complete the task on its own without the rest of the program.

quine code-bowling busy-beaver

Sandbox notes

• The "1024" may change

Answer 10

Sort on an infinite-dimension cube

Given a unit cube in the \$n\$-dimensional space. Assume that the vertices of the cube has coordinate \$(x_0, x_1, x_2, \dots, x_n)\$ where \$x_i \in \{0,1\} \forall i\in \mathbb N, 0\le i<n\$.

It's possible to number all vertices with non-negative integers less than \$2^n\$. In this challenge, the vertex with coordinate \$(x_0, x_1, x_2, \dots, x_n)\$ will be assigned with number \$2^0\times x_0+2^1\times x_1+\dots+2^n\times x_n\$.

Each vertex can hold an integer.

In this challenge, you can assume \$n\$ contains a very large (practically infinite) value.

---

Given \$4096\$ items placing in vertex 0 - vertex 4095, you're to sort them. Other vertices contain undefined values, and may be modified by the program.

However, the program cannot directly access the values held by the vertices. You can only control a memory pointer M, which always lie at a vertex of the cube (call this vertex V). Initially M is at the coordinate \$(0,0,0,\dots)\$. This memory pointer can store exactly 1 integer value.

The following operations on the memory pointer M are alllowed:

• Store the value held by V into memory of M.
• Write the value stored by M into V.
• Compare value stored by M and value held by V. This operation should report to the program 3 different values based on whether the comparison is \$<\$, \$=\$ or \$>\$.
• Move along an edge (in the direction specified by the program) of the cube. This corresponds to changing exactly 1 coordinate of M from 0 to 1, or vice versa.

Your score is the distance traveled by the memory pointer.

---

A psuedo-code sample interaction library may be:

obj[Infinity] = {[4096 values]}
ptr = 0, cry = undefined
function move(i): ptr = ptr xor (1 shl i)
function carry(): cry = obj[ptr]
function place(): obj[ptr] = cry
function compare(): return sgn(obj[ptr] - cry)

You can write functions, use IO, or anyway to interact. Lowest move callings win.

Answer 11

Golf a regex that matches syntactically valid programs in the language of your choice.

1: Pick a programming language, P, that meets these requirements:

• P is known to be Turing-Complete.
• P has a freely available and working compiler or interpreter.

2: Create a regular expression, R, such that:

• R matches any string that is a syntactically valid program of P.
• R rejects any string that is a syntactically invalid program of P

3: Golf R. Shortest regex wins.

Answer 12

Largest and Smallest Numbers Printable

code-challenge palindrone restricted-source

Related: Largest Number Printable

Your goal is to write code that produces a large number. However, when your code is reversed, you must output a small number.

Rules

• No constants over 10 (like the other challenge)
• No numeric literals
• No infinite numbers
• Each program can only output one number
• You must have at least two bytes in your program.
• Your small number must be less than your large number.

Scoring:

Your score is: \$\frac{code~length}{N_{large} - N_{small}}\$. Smallest score wins.

Answer 13

The Tiniest Generic Evolutionary AI

---

code-golf ai test-battery

---

Introduction

The smallest program you can make (measured in bytes) that builds evolving AIs that parses unknown text string A into unknown text string B that still evolves.

All languages are options. Internet connectivity is allowed (but not providing any specific links). The AI must have a choice of commands (allowing variables) from a Turing Complete instruction set.

---

Scoring

Scoring is two fold: N = Number of bytes of program (ignoring size of AIs generated)

T = The average generations (generations of 200 AIs or less) before your program can evolve an AI that can do the 5 test cases.

Score = 1000/(N*T)

---

Challenge

Rules: Using the fewest bytes possible, create a generic evolutionary AI that will evolve to parse one supplied but previously unknown string into another supplied but previously unknown string.

What qualifies as an evolutionary AI in this context:

Your Code
Takes an input string
Takes a seed AI Instruction Set(s)
Runs AI Instruction Sets
Rates Each AI Instruction Set against others and against test strings
Evolves AI to create a new set of AI Instruction Set(s) through random mutation and breeding of existing AIs.
=================
AI Code
Is not written by you (except for possibly a seed AI), to be created by your program instead.
Uses a set of *available* instructions that are or are inspired by a known Turing complete instruction set (such as RISC)
Should consist of references to the available instructions and values for them.

1. The code you write does not parse the strings directly. Instead, it writes output that is a collection of instructions, and reads in a collection of instructions and applies these instructions. (Ugly as it may be, eval is allowed).

2. It reads in multiple optional instruction sets.

3. It rates those instruction sets based on which gets closest to parsing the input string into the target string.

4. The best performing instructions sets are encouraged in some way.

5. The worst performing instruction sets are discouraged and/or eliminated in some way.

6. Using existing AI-oriented libraries is discouraged.

7. Allowing evolutionary AIs to use develop using a turing-complete set of instructions is encouraged. (Example solution uses a modified RISC instruction set.)

8. Instruction sets must be able to mutate (randomly change) between generations. They are allowed to breed (selectively change) between generations as well.

9. Multiple iterations of comparing and evolving instructions sets is possible.

10. How quickly your AIs evolve or how well they do the job doesn't matter so much as they can get better at the task over iterations.

11. A seed starting instruction set is allowed. If your solution requires an inputed file for an initial instruction set, a functional example is required and counts towards the byte count.

12. It handles if an instruction set it runs fails to complete, or times out if an AI instruction set goes on too long (default to 30 seconds).

13. Program must accept in one arbitrary string from a source. (Your choice of a generic commonly used source, such as a web form, command line, or file). It outputs each AI instruction set's result in a similar format it took them in. It may also optionally accept a starter AI set of instructions.

14. The AI code never gets to interact with the test string it's being graded against.

15. Your program cannot do any string conversions on the input string on its own, only may act as it's instructed to by the AI.

16. A seed AI is not allowed to have anything more than a start, end, or return call of some kind (it must evolve any processing steps on its own).

---

Test Cases:

Can the program evolve an AI that approaches being capable of string conversion of an unknown conversion? (It is recommended not to build the AI to these specific test cases, these are for the point of testing genericness. Do not specifically target these cases until reporting results, and others testing your program may test them against other string conversions and rate accordingly.)

Five examples follow -

abcdefghijklmnopqrstuvwxyz

will be converted into

zyxwvutsrqponmlkjihgfedcba

or possibly

1010101100110101011001

will be converted into

0101010011001010100110

or possibly

"Mary had a little lamb."

will be converted into

"Gary had a little ham."

or possibly

"Banana"

will be converted to

"Banananananananananananananananana."

Or maybe

The entire text of the Bible

will be converted to

The entire text of the Bible, but every instance of "sheep" is replaced with "codfish".

---

Short Diagram of interaction.

   STEP 1                         STEP 2                     STEP 3  ...

 Input String           ->
 Expected Output String ->   Your Code Starts  ->    Assorted AI Instruction sets. ->      ->        ->       ->      Your Code Processes AI Instruction Sets -> Your code compares, mutates, and breeds AIs to create new generation -> Return to Step 3
 Seed AI                ->                     (Example: AI1 -> Start(Input); Output(Input)
                                                         AI2 -> Start(Input); CP(Mem1, Mem2); Output (Mem2);)

---

Example

An on-a-whim project done that roughly followed these rules and inspired this challenge that ran <1000 lines of code (although short, it did not aim for minimal characters.)

myLittleAI

Answer 14

Rotations Required

Given input 2 values:

\$x >= 0\$ :Distance to travel (float)

\$r>0\$ :Radius of wheel (float)

Output the number of rotations required by the wheel to travel that distance.

Constraints:

Your code must not contain any digits.

You cannot use pi functions (math.pi)

Output must be an integer.(In case exact int is not obtained, floor it) 1.0 is not a valid output, it should be 1.

Test Cases

x       r    o/p
50      1    7
0       34   0
50      0.3  26
44      33   0
5.5     5.5  0
105     5    3
155     5    4
6.28318 1    1 #This signifies that pi was approximated to 3.1419

Scoring:

Score= No. of bytes+20/number of digits taken for pi after decimal point

If you have taken more than 10 digits:

Score= No. of bytes

Answer 15

Write a Self-Hosting Ouroboros: each quine produces the next quine AND its interpreter

My meta-questions, please give feedback and/or add your own:

• Too elaborate or long post?
• Rules too strict? Too lax?
• Not having a deadline: good or bad idea?

---

A Quine is a program that prints its own source code as output when it is run.

A Self-Hosting Quine (which is something I just made up, although I'm sure it exists already) is a quine that also produces an interpreter/compiler/emulator/whatever for itself (from now on I will just say "interpreter").

I believe this actually means that a lot of essential functionality must be "circularly defined" - for example, to print output, the interpreter must rely on the parent interpreter's ability to print output. So maybe we should call this a Von Munchausen Quine?

An Ouroboros Program or Quine Relay is a quine that prints a different quine, which then prints yet another program, and so on, until the last quine produces the original quine. See this famous example that cycles through over a hundred languages.

A Self-Hosting Ouroboros, then, is quine that produces a program in another language, and also produces an interpreter for that language. The interpreter should be in the current language, so that the next quine can immediately be run and produce the quine after that.

Tangent: obviously, the idea can also be extended to interpreter multiquines but that can be another challenge. Let's make Von Munchausen's Ouroboros first!

Rules

• The ouroboros must be able to make a complete cycle
• Score by total quines in chain / shortest source code (in bytes) in the chain (bytes to allow non-textual outputs)
• Empty quines and interpreters do not count - two character minimum
• Code-golf languages allowed
• No languages defined just for this challenge - no "I define language x to always produce quine y in C plus the complete GCC compiler when fed any input"-stuff please
• Quines must be valid code in their programming languages
• Interpreters that are partial language implementations are fine, however:
  • it must be able to run the quine, and produce the next quine (obviously).
  • it should be able to run any other correct code that is limited to the same language subset¹. No hyperfitting²!
  • for the sake of code golfing it may accept incorrect code that a normal interpreter should not (the quine is already restricted to correct code anyway)

Clarifications

Yes, you can make a quine that produces itself and its own interpreter

Counts as a 1-chain ouroboros.

What would an "interpreter" for machine code be?

An emulator. Which of course needs some way to load a program and produce the output. You may define a fictional simplified, minimal hardware set-up to do so. For example: a (partial) Z80 emulator where:

• two hardware ports are connected to send output bytes to (one for interpreter, one for quine). Are those bytes interpreted as raw bytes/ASCI/UTF8 text/whatever? Up to you!
• the program is already loaded in memory, at whatever address is most convenient (quine too big to fit in the addressable memory space? Define an input port to scan bytes from I guess :P)
• the PC (program counter), and SP (stack pointer) registers initiate at whatever value is most convenient for creating a quine in Z80 opcode

Obviously, no set-ups with fictional ROM that just happens to contain a new quine, or stuff like that (even though this would be hard to really abuse, since that ROM would still need to be implemented in the emulator).

Am I seriously expecting anyone to create an emulator like this? No, but let's keep the possiblity open (some stack machines might be code golf-friendly enough for the challenge).

"Borrowing" snippets from each other is encouraged, but give accreditation and link to sources!

Because we all really just want to see how long this can get, no? Besides, whatever you take probably has to be heavily modified to fit it in your existing ouroboros chain anyway. Sharing is caring, and accreditation is the decent thing to do.

No dead-line, nor will a winner be selected. Just make as long a chain as possible.

---

¹ You wrote an interpreter for a subset of Rust, but it doesn't feature the borrow checker? That is fine long as:

• it works with correct Rust code limited to the language subset
• it works with the quine itself
• the quine itself is correct rust code

² Example of what I do and do not consider hyperfitting: if your interpreter can deal with for(var i; i < 10; i++) { a[i] = i; } but crashes without the enclosing {} because it expects them to designate code blocks, that counts as a partial implementation. If var only expects i, or < only expects i and 10? Hyperfitting. If var only accepts single letter names, and < only expects variables on the left and literals on the right? Probably hyperfitting but debatable.

Answer 16

Unicode encoder

Do Invent your own Unicode 7.0.0 encoding (as efficient as possible) with score 317754(the lowest possible score). Shortest encode+decode program win.

You can either write two programs doing encode and decode, or write one with argument/input method difference deciding whether it's encoding or decoding

As you may know, the Unicode standard has room for 1,114,111 code points, and each assigned code point represents a glyph (character, emoji, etc.).

Most code points are not yet assigned.

Current Unicode implementations take a lot of space to encode all possible code points (UTF-32 takes 4 bytes per code point, UTF-16: 2 to 4 bytes, UTF-8: 1 to 4 bytes, etc.)


Task
-

Today, your task is to implement your own Unicode implementation, with the following rules:

- Write an encoder and a decoder in any language of your choice
- The encoder's input is a list of code points (as integers) and it outputs a list of bytes (as integers) corresponding to your encoding.
- The decoder does the opposite (bytes => code points)
- Your implementation has to cover all Unicode 7.0.0 assigned code points
- It has to stay backwards-compatible with ASCII, i.e. encode Basic latin characters (U+0000-U+007F) on one byte, with 0 as most significant bit.
- Encode all the other assigned code points in any form and any number of bytes you want, as long as there is no ambiguity (i.e. two code points or group of code points can't have the same encoding and vice versa)
- Your implementation doesn't have to cover UTF-16 surrogates (code points U+D800-U+DFFF) nor private use areas (U+E000-U+F8FF, U+F0000-U+10FFFF)
- Your encoding must be context-independant (i.e. not rely on previously encoded characters) and does NOT require self-synchronization (i.e. each byte doesn't have to infer where it's located in the encoding of a code point, like in UTF-8).

To sum up, here are the blocks that you have to cover, in JSON:

[
  [0x0000,0x007F], // Basic Latin
  [0x0080,0x00FF], // Latin-1 Supplement
  [0x0100,0x017F], // Latin Extended-A
  [0x0180,0x024F], // Latin Extended-B
  [0x0250,0x02AF], // IPA Extensions
  [0x02B0,0x02FF], // Spacing Modifier Letters
  [0x0300,0x036F], // Combining Diacritical Marks
  [0x0370,0x03FF], // Greek and Coptic
  [0x0400,0x04FF], // Cyrillic
  [0x0500,0x052F], // Cyrillic Supplement
  [0x0530,0x058F], // Armenian
  [0x0590,0x05FF], // Hebrew
  [0x0600,0x06FF], // Arabic
  [0x0700,0x074F], // Syriac
  [0x0750,0x077F], // Arabic Supplement
  [0x0780,0x07BF], // Thaana
  [0x07C0,0x07FF], // NKo
  [0x0800,0x083F], // Samaritan
  [0x0840,0x085F], // Mandaic
  [0x08A0,0x08FF], // Arabic Extended-A
  [0x0900,0x097F], // Devanagari
  [0x0980,0x09FF], // Bengali
  [0x0A00,0x0A7F], // Gurmukhi
  [0x0A80,0x0AFF], // Gujarati
  [0x0B00,0x0B7F], // Oriya
  [0x0B80,0x0BFF], // Tamil
  [0x0C00,0x0C7F], // Telugu
  [0x0C80,0x0CFF], // Kannada
  [0x0D00,0x0D7F], // Malayalam
  [0x0D80,0x0DFF], // Sinhala
  [0x0E00,0x0E7F], // Thai
  [0x0E80,0x0EFF], // Lao
  [0x0F00,0x0FFF], // Tibetan
  [0x1000,0x109F], // Myanmar
  [0x10A0,0x10FF], // Georgian
  [0x1100,0x11FF], // Hangul Jamo
  [0x1200,0x137F], // Ethiopic
  [0x1380,0x139F], // Ethiopic Supplement
  [0x13A0,0x13FF], // Cherokee
  [0x1400,0x167F], // Unified Canadian Aboriginal Syllabics
  [0x1680,0x169F], // Ogham
  [0x16A0,0x16FF], // Runic
  [0x1700,0x171F], // Tagalog
  [0x1720,0x173F], // Hanunoo
  [0x1740,0x175F], // Buhid
  [0x1760,0x177F], // Tagbanwa
  [0x1780,0x17FF], // Khmer
  [0x1800,0x18AF], // Mongolian
  [0x18B0,0x18FF], // Unified Canadian Aboriginal Syllabics Extended
  [0x1900,0x194F], // Limbu
  [0x1950,0x197F], // Tai Le
  [0x1980,0x19DF], // New Tai Lue
  [0x19E0,0x19FF], // Khmer Symbols
  [0x1A00,0x1A1F], // Buginese
  [0x1A20,0x1AAF], // Tai Tham
  [0x1AB0,0x1AFF], // Combining Diacritical Marks Extended
  [0x1B00,0x1B7F], // Balinese
  [0x1B80,0x1BBF], // Sundanese
  [0x1BC0,0x1BFF], // Batak
  [0x1C00,0x1C4F], // Lepcha
  [0x1C50,0x1C7F], // Ol Chiki
  [0x1CC0,0x1CCF], // Sundanese Supplement
  [0x1CD0,0x1CFF], // Vedic Extensions
  [0x1D00,0x1D7F], // Phonetic Extensions
  [0x1D80,0x1DBF], // Phonetic Extensions Supplement
  [0x1DC0,0x1DFF], // Combining Diacritical Marks Supplement
  [0x1E00,0x1EFF], // Latin Extended Additional
  [0x1F00,0x1FFF], // Greek Extended
  [0x2000,0x206F], // General Punctuation
  [0x2070,0x209F], // Superscripts and Subscripts
  [0x20A0,0x20CF], // Currency Symbols
  [0x20D0,0x20FF], // Combining Diacritical Marks for Symbols
  [0x2100,0x214F], // Letterlike Symbols
  [0x2150,0x218F], // Number Forms
  [0x2190,0x21FF], // Arrows
  [0x2200,0x22FF], // Mathematical Operators
  [0x2300,0x23FF], // Miscellaneous Technical
  [0x2400,0x243F], // Control Pictures
  [0x2440,0x245F], // Optical Character Recognition
  [0x2460,0x24FF], // Enclosed Alphanumerics
  [0x2500,0x257F], // Box Drawing
  [0x2580,0x259F], // Block Elements
  [0x25A0,0x25FF], // Geometric Shapes
  [0x2600,0x26FF], // Miscellaneous Symbols
  [0x2700,0x27BF], // Dingbats
  [0x27C0,0x27EF], // Miscellaneous Mathematical Symbols-A
  [0x27F0,0x27FF], // Supplemental Arrows-A
  [0x2800,0x28FF], // Braille Patterns
  [0x2900,0x297F], // Supplemental Arrows-B
  [0x2980,0x29FF], // Miscellaneous Mathematical Symbols-B
  [0x2A00,0x2AFF], // Supplemental Mathematical Operators
  [0x2B00,0x2BFF], // Miscellaneous Symbols and Arrows
  [0x2C00,0x2C5F], // Glagolitic
  [0x2C60,0x2C7F], // Latin Extended-C
  [0x2C80,0x2CFF], // Coptic
  [0x2D00,0x2D2F], // Georgian Supplement
  [0x2D30,0x2D7F], // Tifinagh
  [0x2D80,0x2DDF], // Ethiopic Extended
  [0x2DE0,0x2DFF], // Cyrillic Extended-A
  [0x2E00,0x2E7F], // Supplemental Punctuation
  [0x2E80,0x2EFF], // CJK Radicals Supplement
  [0x2F00,0x2FDF], // Kangxi Radicals
  [0x2FF0,0x2FFF], // Ideographic Description Characters
  [0x3000,0x303F], // CJK Symbols and Punctuation
  [0x3040,0x309F], // Hiragana
  [0x30A0,0x30FF], // Katakana
  [0x3100,0x312F], // Bopomofo
  [0x3130,0x318F], // Hangul Compatibility Jamo
  [0x3190,0x319F], // Kanbun
  [0x31A0,0x31BF], // Bopomofo Extended
  [0x31C0,0x31EF], // CJK Strokes
  [0x31F0,0x31FF], // Katakana Phonetic Extensions
  [0x3200,0x32FF], // Enclosed CJK Letters and Months
  [0x3300,0x33FF], // CJK Compatibility
  [0x3400,0x4DBF], // CJK Unified Ideographs Extension A
  [0x4DC0,0x4DFF], // Yijing Hexagram Symbols
  [0x4E00,0x9FFF], // CJK Unified Ideographs
  [0xA000,0xA48F], // Yi Syllables
  [0xA490,0xA4CF], // Yi Radicals
  [0xA4D0,0xA4FF], // Lisu
  [0xA500,0xA63F], // Vai
  [0xA640,0xA69F], // Cyrillic Extended-B
  [0xA6A0,0xA6FF], // Bamum
  [0xA700,0xA71F], // Modifier Tone Letters
  [0xA720,0xA7FF], // Latin Extended-D
  [0xA800,0xA82F], // Syloti Nagri
  [0xA830,0xA83F], // Common Indic Number Forms
  [0xA840,0xA87F], // Phags-pa
  [0xA880,0xA8DF], // Saurashtra
  [0xA8E0,0xA8FF], // Devanagari Extended
  [0xA900,0xA92F], // Kayah Li
  [0xA930,0xA95F], // Rejang
  [0xA960,0xA97F], // Hangul Jamo Extended-A
  [0xA980,0xA9DF], // Javanese
  [0xA9E0,0xA9FF], // Myanmar Extended-B
  [0xAA00,0xAA5F], // Cham
  [0xAA60,0xAA7F], // Myanmar Extended-A
  [0xAA80,0xAADF], // Tai Viet
  [0xAAE0,0xAAFF], // Meetei Mayek Extensions
  [0xAB00,0xAB2F], // Ethiopic Extended-A
  [0xAB30,0xAB6F], // Latin Extended-E
  [0xABC0,0xABFF], // Meetei Mayek
  [0xAC00,0xD7AF], // Hangul Syllables
  [0xD7B0,0xD7FF], // Hangul Jamo Extended-B
  [0xF900,0xFAFF], // CJK Compatibility Ideographs
  [0xFB00,0xFB4F], // Alphabetic Presentation Forms
  [0xFB50,0xFDFF], // Arabic Presentation Forms-A
  [0xFE00,0xFE0F], // Variation Selectors
  [0xFE10,0xFE1F], // Vertical Forms
  [0xFE20,0xFE2F], // Combining Half Marks
  [0xFE30,0xFE4F], // CJK Compatibility Forms
  [0xFE50,0xFE6F], // Small Form Variants
  [0xFE70,0xFEFF], // Arabic Presentation Forms-B
  [0xFF00,0xFFEF], // Halfwidth and Fullwidth Forms
  [0xFFF0,0xFFFF], // Specials
  [0x10000,0x1007F], // Linear B Syllabary
  [0x10080,0x100FF], // Linear B Ideograms
  [0x10100,0x1013F], // Aegean Numbers
  [0x10140,0x1018F], // Ancient Greek Numbers
  [0x10190,0x101CF], // Ancient Symbols
  [0x101D0,0x101FF], // Phaistos Disc
  [0x10280,0x1029F], // Lycian
  [0x102A0,0x102DF], // Carian
  [0x102E0,0x102FF], // Coptic Epact Numbers
  [0x10300,0x1032F], // Old Italic
  [0x10330,0x1034F], // Gothic
  [0x10350,0x1037F], // Old Permic
  [0x10380,0x1039F], // Ugaritic
  [0x103A0,0x103DF], // Old Persian
  [0x10400,0x1044F], // Deseret
  [0x10450,0x1047F], // Shavian
  [0x10480,0x104AF], // Osmanya
  [0x10500,0x1052F], // Elbasan
  [0x10530,0x1056F], // Caucasian Albanian
  [0x10600,0x1077F], // Linear A
  [0x10800,0x1083F], // Cypriot Syllabary
  [0x10840,0x1085F], // Imperial Aramaic
  [0x10860,0x1087F], // Palmyrene
  [0x10880,0x108AF], // Nabataean
  [0x10900,0x1091F], // Phoenician
  [0x10920,0x1093F], // Lydian
  [0x10980,0x1099F], // Meroitic Hieroglyphs
  [0x109A0,0x109FF], // Meroitic Cursive
  [0x10A00,0x10A5F], // Kharoshthi
  [0x10A60,0x10A7F], // Old South Arabian
  [0x10A80,0x10A9F], // Old North Arabian
  [0x10AC0,0x10AFF], // Manichaean
  [0x10B00,0x10B3F], // Avestan
  [0x10B40,0x10B5F], // Inscriptional Parthian
  [0x10B60,0x10B7F], // Inscriptional Pahlavi
  [0x10B80,0x10BAF], // Psalter Pahlavi
  [0x10C00,0x10C4F], // Old Turkic
  [0x10E60,0x10E7F], // Rumi Numeral Symbols
  [0x11000,0x1107F], // Brahmi
  [0x11080,0x110CF], // Kaithi
  [0x110D0,0x110FF], // Sora Sompeng
  [0x11100,0x1114F], // Chakma
  [0x11150,0x1117F], // Mahajani
  [0x11180,0x111DF], // Sharada
  [0x111E0,0x111FF], // Sinhala Archaic Numbers
  [0x11200,0x1124F], // Khojki
  [0x112B0,0x112FF], // Khudawadi
  [0x11300,0x1137F], // Grantha
  [0x11480,0x114DF], // Tirhuta
  [0x11580,0x115FF], // Siddham
  [0x11600,0x1165F], // Modi
  [0x11680,0x116CF], // Takri
  [0x118A0,0x118FF], // Warang Citi
  [0x11AC0,0x11AFF], // Pau Cin Hau
  [0x12000,0x123FF], // Cuneiform
  [0x12400,0x1247F], // Cuneiform Numbers and Punctuation
  [0x13000,0x1342F], // Egyptian Hieroglyphs
  [0x16800,0x16A3F], // Bamum Supplement
  [0x16A40,0x16A6F], // Mro
  [0x16AD0,0x16AFF], // Bassa Vah
  [0x16B00,0x16B8F], // Pahawh Hmong
  [0x16F00,0x16F9F], // Miao
  [0x1B000,0x1B0FF], // Kana Supplement
  [0x1BC00,0x1BC9F], // Duployan
  [0x1BCA0,0x1BCAF], // Shorthand Format Controls
  [0x1D000,0x1D0FF], // Byzantine Musical Symbols
  [0x1D100,0x1D1FF], // Musical Symbols
  [0x1D200,0x1D24F], // Ancient Greek Musical Notation
  [0x1D300,0x1D35F], // Tai Xuan Jing Symbols
  [0x1D360,0x1D37F], // Counting Rod Numerals
  [0x1D400,0x1D7FF], // Mathematical Alphanumeric Symbols
  [0x1E800,0x1E8DF], // Mende Kikakui
  [0x1EE00,0x1EEFF], // Arabic Mathematical Alphabetic Symbols
  [0x1F000,0x1F02F], // Mahjong Tiles
  [0x1F030,0x1F09F], // Domino Tiles
  [0x1F0A0,0x1F0FF], // Playing Cards
  [0x1F100,0x1F1FF], // Enclosed Alphanumeric Supplement
  [0x1F200,0x1F2FF], // Enclosed Ideographic Supplement
  [0x1F300,0x1F5FF], // Miscellaneous Symbols and Pictographs
  [0x1F600,0x1F64F], // Emoticons
  [0x1F650,0x1F67F], // Ornamental Dingbats
  [0x1F680,0x1F6FF], // Transport and Map Symbols
  [0x1F700,0x1F77F], // Alchemical Symbols
  [0x1F780,0x1F7FF], // Geometric Shapes Extended
  [0x1F800,0x1F8FF], // Supplemental Arrows-C
  [0x20000,0x2A6DF], // CJK Unified Ideographs Extension B
  [0x2A700,0x2B73F], // CJK Unified Ideographs Extension C
  [0x2B740,0x2B81F], // CJK Unified Ideographs Extension D
  [0x2F800,0x2FA1F], // CJK Compatibility Ideographs Supplement
  [0xE0000,0xE007F], // Tags
  [0xE0100,0xE01EF]  // Variation Selectors Supplement
]

Total: 116,816 code points.

Scoring
--

Your score is the number of bytes that your encoder outputs when you feed it with all the 116,816 possible code points (in one time or separately).

code-golf kolmogorov-complexity

Answer 17

Forcing a kernel panic from a mountaintop

This is a thought resulting from a curious incident where C# code opening file apparently caused a BSOD. In the conclusion, it was due to a faulty driver, but from that a thought came up --- can one cause a kernel panic (or BSOD) using managed code exclusively?

Why?

Typically in such environment, there are many compile-time and run-time checks that safeguard the code from doing something that would cause a kernel panic. For a mature managed environment, it should be impossible to cause the operating system to arrive into a bad state. In the case, though it was C# code, the fact that a faulty driver was involved breached the walled garden. But can we breach it from within?

Rules

• The code must be managed in some fashion (e.g. Java, C#, VB.NET), and normally comes with both compile-time and run-time checks.
• The code should be running in a virtual machine or equivalent. (e.g. Java's JVM or .NET's AppDomain)
• The code should NOT rely on any external anything. No extern declarations, no networking, no dodgy APIs.
• The code should NOT use any construct which allow direct access to resources (e.g. unsafe in C#)
• The code should use only the native libraries & API available as part of its usual environment.
• Throwing an exception is not sufficient. To qualify, the code must result in a kernel panic.

Criteria

Essentially a code-golf -

• The less code to kernel panic, the better
• The fewer dependencies the code uses to make it happen, the better
• The code that consistently causes a kernel panic is better than one that only does it sometimes

Answer 18

Play snake on a 50*50 grid. The snake will start at length 3, heading (2,0) with body (1,0) and (0,0). It shouldn't bump into wall or itself. There is always one food, which increases the length of snake by 1 when eaten.

Smallest amount of steps till there's no space to place food win. Flexible I/O, anyway it doesn't matter.

Vote on whether the food placer is transparent and allow food manipulation(Up for yes, down for no)

Answer 19

No-alphanumeric code exec

Answer 20

HTML-tac-toe

Build a one-player tic-tac-toe game with only HTML and CSS.

Introduction

You can do just about anything with a fully-featured programming language, but how much can you accomplish on a Neopets petpage? Inspired by http://www.neopets.com/~vuh

Challenge

Build a one-player tic-tac-toe game with only HTML and CSS.

• Use no more than one file.
• GIFs (including animations), PNGs, and JPEGs are allowed.
• Flash, embedded scripts, iframes, and JavaScript are not allowed.
• It must work in the at least two standard browsers (FF, Chrome, Safari, Opera, IE)

Inputs: The player will click on a space when it's their turn to move there.

Outputs: The page will show the current board state at all times. The page will play an optimal move whenever the player moves, unless the game is over.

You're free to decide who starts and who has X or O.

Scores

• -10 per image
• -1 per opening bracket or brace (< / { )

Brownie points for design, flair, and new tricks!

Example Input and Output

Input:

Click on the top left of an empty grid

Output:

Grid shows my mark where I clicked and the opposite mark in the left middle or top middle.

Answer 21

Bit flipper

Given a string s and a positive number n, return the string s with n random bits flipped. (A random number can be generated in any way, including pseudo-random number generators)

Example:

Before:

Hello World

After (n = 2, 2 bits flipped):

Hello wOrld

Answer 22

You can't tell me what to do!!!

Intentionally break as many coding conventions as possible while crafting a working Hello World

coding-challenge hello-world obfuscation

For each language, a coding convention standard will be selected. The following is the current list:

javascript -> Google's Style Guide

PHP -> PSR-2

C++ -> ISO C++ Style Guide

Python -> PEP-8

The maximum file length is 6000 characters. Any code beyond the first 6000 will not count towards broken conventions. (Using conventions that you have set to break after the 6000 point, however, will count against you.)

If you do not see your language, you may choose one of the most common coding standards for your language, and use that, and (hopefully) it will be noticed and added to the list. Each language is its own competition. (For example: If your code is in Ruby, you're not competing against C++ code)

This is the coding equivalent of an ugly baby contest, and pushes you to think outside the box (possibly way too far outside the box). The goal is to write a 'simple' Hello World program. However, you have to do it while breaking as many coding conventions as possible, and being as ugly as possible (but still working!)

The advantages of this puzzle are multi-purpose. This is to challenge the coder to separate long-standing habits (which generally follow coding conventions) from functionality - to encourage creativity. Further, it also serves as a reverse example to demonstrate when coding conventions are a help vs a hindrance.

Remember, ugly doesn't have to mean gibberish or unnecessarily long or poorly running. In fact, code length or runtime do not factor into the evaluation.

For example, you could write procedural code using only classes, use an eval() to declare constants, or use only use variable names using characters that have nothing to do with what the variable does, reverse indentation, or rely exclusively on gotos in an interpreted language. The only thing your code has to do is output "Hello World" to the command line or an equivalent.

Each answer should list and link to coding conventions it breaks and receives 1 point for each broken code convention (but instant total of zero points the code follows any coding convention it says its breaking). If a voter agrees it violates all the listed coding conventions, upvote the code that violates the most while still functioning. (Accidentally violating coding conventions, however, does not count. Each one violated coding convention must be documented and intentional.)

Note: For each coding convention taken on, it must be consistently broken across the entire program. Following the convention even once invalidates your entire code. Habits are your enemy. Further note: If you declare you're breaking a convention, you MUST break it. If it's not applicable, it doesn't count.

Alternate Scoring method:

Don't like the "call your shot and then try to make it" scoring method? Do you have a readily available git functionality? Does the coding convention have a convenient git-hook for code style enforcement? Fear not, you have the option for an alternate scoring method: 1. Write up your code. 2. Run it through the git commit with the hook active. 3. If your hook auto-changes code, commit it, and do step 4. If it gives you coding style errors and rejects the commit, count the errors; you get one point for each error and skip to step 5. If you break git due to the hook crashing, list the broken code enforcement, add 50 points, and try again with a different code-enforcement hook. (You CANNOT be an author or contributor to any git-hook before you test against it. This is considered cheating and will be disqualify you.) 4. If your hook auto-changes code to fit style enforcement, do a git-diff between your code and the code it committed. Each change is one point. 5. Total your points. List your points as an alternate score in your answer's header. List the code-enforcement hooks you tested it against.

I'm personally not a fan of this scoring method as it allows accidental points and becomes more like it's testing the enforcement hook rather than creative code style breaking, but some like the more computer-controlled scoring method... so there ya go.

Sandbox Reminder: Sandbox is a place for constructive criticism. Saying, "I don't like it" or "I wouldn't do it" isn't constructive criticism. Last time I had this in the sandbox, most criticism was built on disliking the type of challenge, not actually building it properly. If you don't like the challenge concept, then just don't do it. If you have legitimate suggestions on how to make the challenge better then do so. I will do my best to address legitimate points.

Standard Example Answer format

---

My Oh so wrong Hello world - PHP - Attempting 2 points

Breaking conventions in PSR-2:

• breaking "Opening braces for classes MUST go on the next line, and closing braces MUST go on the next line after the body."
• breaking "All PHP files MUST end with a single blank line."

--

<?php
class hiworld{public $printme = "Hello World"}
$hiworld = new hiworld;
echo $hiworld->$print; 
?>

---

Alternate Example Answer format

---

My Oh so wrong and totally fake Hello world - PHP - Alt.Points(53)

<?php
class hiworld{public $printme = "Hello World"}
$hiworld = new hiworld;
echo $hiworld->$print; 
?>

Attempted with:

50 pts: PSR-2 Foo's Enforcement Hook: Foo-Checker [http://foo.example.com] (Broke)

3 pts: PSR-2 Bar's Enforcement Hook: Bar-Checker [http://bar.example.com]

---

Deleted Version

Answer 23

Count the Trees

code-golf

Challenge

Given an input consisting of ASCII art of trees such as

  0            <
  |      >       @
  |   @          |    0
  |   |    #     |    |
  |   |    |     |    |
==========================

count the number of trees present (5 in this case).

Rules

Input

• The input might not have all lines at the same length.
• You can take your input from stdin or take it as a string argument.
• There will be a ground as the last line, consisting of = characters.
• All trees have a straight trunk of | characters.
• The crown of the tree can be one of 0@#.
• Each tree will have at least one trunk character.
• You may assume that there is at least one tree.
• Unfortunately, there might be birds (< and >) photobombing the ASCII art. They should be ignored.
• If you find a bird on the ground, then it is dead and another tree will grow in its place tomorrow (carcasses make great fertiliser). In the ASCII art below, there will be two trees tomorrow:

   #
   |   <
=========

Output

• Output the number of trees that are present today and those that will be present tomorrow.

Test cases

  0            <
  |      >       @
  |   @          |    0
  |   |    #     |    |
  |   |    |     |    |
==========================

(5, 5)

   #
   |   <
=========

(1, 2)

 0#@
 |||
 |||
=====

(3, 3)

Answer 24

The heights of Natural Numbers

Every number can be expressed as the product of itself and/or smaller numbers. This is a fundamental feature of our world.

For example 10 can be expressed as the product of 5 and 2, or as the product of 1 and 10.

9 can be expressed as the product of 3 and 3, or 1 and 9.

12 can be expressed as the product of 2 and 6. 6, in turn, can be expressed as the product of 2 and 3. It could also be the product of 3 and 4, and in turn 4 is the product of 2 and 2. Lastly there is 1 and 12.

7 can only be expressed as the product 1 and itself.

The numbers in the products are called factors. Every number has at least 2 factors, itself and 1. Numbers with only those two factors are called prime. Numbers with more than 2 are called composite.

These factors can be written as trees. The root begins with the number itself, and factors are written below, by adding branches to the root.

7 has 1 and 7. This is a short tree. It has one prime.

9 has 3 and 3. This is also a short tree, but it has two branches. It has two primes, but they are both at depth of 1 down the tree.

10 has 5 and 2. Again, short. Again, primes are at depth 1.

12 has 6 and 2, 6 has 3 and 2. This tree has two levels of height. Note that at the second level, every factor is prime, but at the first level, some factors are composite. 12 has also 3 and 4, and 4 becomes 2 and 2 - the tree looks similar to when using 6 and 2, this is called Isomorphic, which comes from the Greek language words for same shape.

In other words, every number has several trees of factors, and each tree has leaves that are prime factors. And every tree has a height, the number of branches one must travel between the root and the furthest leaf.

For example, every number has a tree of height 1. Itself and 1. So.

7 has height 1, because 1x7=7

9 also is height 1, because 3x3=9, and 1x9=9, are both of height 1.

12 is height 2. 3x2x2 becomes 3x4, which becomes 12. There are two branches between 12 and either leaf of 2.

But 12 is also height 1 because it has a different tree of height 1: 1x12=12.

16 is height 3, because 16 becomes 2*8 becomes 2*2*4, becomes 2*2*2*2. But 16 is also depth 1 because 1x16=16. However 16 is not depth 2, because no tree of it's factors has primes up two branches from the root.

Write a program that given an integer n, returns a sequence of the first 100 numbers that have prime factor trees of height n.

Answer 25

Best Mile Time

Introduction

Your friend has been trying to improve his mile time on. Unfortunately, he isn't very good at keeping a steady pace and constantly speeds up and then slows down. He usually runs for many miles at a time and wants to choose the fastest mile of his run to determine his mile time.

Given your friend's distance versus time, determine his fastest mile time for a contiguous mile stretch.

Input

A list of distances (in miles) sampled at an even interval.

Output

The length of the smallest interval during which a distance of at least one mile was traveled.

Rules

• You may assume that the the total distance traveled is at least 1 mile.
• The mile time must be for a continuous time interval.
• Standard loop-holes are forbidden.
• Standard rules apply.
• Please provide a link to test your code as well as an explanation.
• This is fastest-algorithm, so the program with the smallest asymptotic time complexity wins!
• Ties will be broken by fastest run time.

---

Example

Python 3.7, O(n ^ 2)

Try it online!

from typing import List


def fastest_mile_time(distances):
    """Determines the fastest mile time from a list of distances.

    Parameters
    ----------
    distances : List[float]
        The list of distances in miles.

    Returns
    -------
    int
        The length of the smallest interval during which at least one mile was traveled.
    """
    intervals = []
    for i in range(len(distances) - 1):
        for j in range(i + 1, len(distances)):
            if distances[j] - distances[i] >= 1:
                intervals.append((i, j))
                break

    return min(map(lambda x: x[1] - x[0], intervals))

Answer 26

Produce a self-reproducing data structure

Write the shortest code to produce a self-reproducing list, dictionary, array, and so on and so forth. That is, when you index any one of the logically-available items that belongs to the resulting data structure that you have produced, you get the same data structure when you compare the equality between the data structure before you indexed and the data structure after you indexed.

• In order to verify your code with automatically-provided constructions in programming languages, you should pick an operator that compares whether two values are equal (or does type-comparisons, if available).
• If your language does not provide an equality operator, you should simulate an equality operator yourself using operators like - or other operators that do the job of comparing values (as in Acc!, where an explicit comparison operator is not provided.)

Example

This is an example of a validity/equality test of a possible solution in a Python REPL (when you have already produced a list, namely list, where it produces itself at its 0th item). This test simply compares the equality between the non-indexed list and the indexed list:

>>> list
[[...]]
>>> list[0]
[[...]]
>>> list==list[0]
True

However, if the result of the last line (the equality comparison) is not a truthy value in your language (for example False and 0 in Python), then your answer is invalid and should be improved.

Rules

• Your program does not have to take input; neither does it have to explicitly output the data structure. However, your resulting data structure has to be accessible in some way.
• This is a code-golf contest; the shortest answer will win.
• No standard loopholes, please.
• In this challenge, the values on both operands in the equality check should have the same type.
• Your code (both your testing code and your producing code) should not produce any errors; any outputs to stderr are considered non-truthy values and demonstrates that your code is invalid.

  ---

  code-golf array-manipulation

Answer 27

Recursive Sum Up The Digits

Tags: code-golf number integer

Produce the shortest code that sums up all the digits in a number, and after if it still has more than one digit, sum it up again and again until it's with one digit, example: 987 would become 6 since 9 + 8 + 7 is 24, whereas 2 + 4 is 6.

Answer 28

Make it improbable... BUT NOT IMPOSSIBLE

You must make a program that outputs truly once in a while. However, making it have output falsy all the time is not acceptable.

Rules

• Standard loopholes are forbidden.
• You may use any of accepted I/O formats.
• Your program must be possible to output a truly value.
• When not outputting a truly value, you may either output a falsy value or not output anything at all.
• You may output two or more values, however if it contains a truly value, then the output is considered truly.
• The probability of outputting a truly value must be at most 1/2.
• Your program must not take/use an input.
• Using non-deterministic but non-random(Such as getting the time) is prohibited. However, if date etc. is used in the builtin random function, it is allowed.
• The program must theoretically always terminate or stop outputting anything.
• You may assume that you have a fast enough computer and large enough memory.
• Your program should not be affected by raising the maximum value of a data type. You may still use unaffected constants.
• Data types must be following its spec: ie. for an unbounded arbituary precision integer type, you may assume that it can go as high as you want(but you are not allowed to increment until an error as in the rule above), but a double-precision floating-point format still has 22-bit fraction and 8-bit exponent.
• Score is calculated as: P^l-1.5l, where P is the probability and l is the byte length.

Example(s)

JavaScript
alert(Math.random()<0.1)
P=0.1, l=24 => Score=23.534

The lowest score wins!

Answer 29

I reverse the source code, you keep the output

code-golf string source-layout

Yet another blatant rip-off of a rip-off of a rip-off of a rip-off. Go upvote those!

Your task, if you wish to accept it, is to write a program/function that outputs/returns its own output. The tricky part is that if I reverse your source code, the output must be preserved.

Examples

Let's say your code is ABC and the corresponding output is XYZ. If I run CBA, the output must also be XYZ

Answer 30

print 1000 digits of \$\pi\$ base 3

The question was on hold for "unclear what you're asking". Really? What was the real reason?

No input. We need to compute and print the values of \$\pi\$ and Euler constant \$\gamma\$
to \$1000\$ digits after decimal point
in base \$3\$ with digits \$-1,0,1\$ represented as -,0,+ respectively.

For \$\pi\$ output is likely starts with +0.0++-+++-000-0++-++0+-++++++00--++.
\$\pi\$ can be computed as series of \$\tan^{-1}\$, \$\gamma\$ -- like here, or any other method will do if fast enough to provide needed accuracy for at most \$60\$ seconds for both numbers.

Storing or using entire pre-computed values are forbidden.
One may though use wolframalpha regular-base-3 values for checking their output -- for \$\pi\$ and \$\gamma\$ (hit "More digits" some times to get \$1000\$).

Scoring method is code-golf, but TIO should run at most \$60\$ seconds.
Good luck. Please fell free to improve this post.