The "Fizz-Buzz test" is an interview question designed to help filter out the 99.5% of programming job candidates who can't seem to program their way out of a wet paper bag. The text of the programming assignment is as follows:

"Write a program that prints the numbers from 1 to 100. But for multiples of three print "Fizz" instead of the number and for the multiples of five print "Buzz". For numbers which are multiples of both three and five print "FizzBuzz"." - FizzBuzz Test

• ARMHF ASM
• x64 ASM
• x86 ASM
• C
• C++
• C#
• C# w/Compiled Expression Trees
• C# w/IL
• F#
• G-code (Klipper) 2
• Homespring 3
• Java
• JavaScript
• OpenSCAD
• Pattern-Lang 1
• PowerShell
• PowerShell-Ninja
• Python 3
• Ruby
• Visual Basic

Create a Pull Request with your solution. Be sure to specify the following in your PR:

• Language
• Compiler/SDK Required to Build
  • Include the specific OS and repository to obtain the Compiler/SDK from. Linux or Windows accepted.
• Script to Perform the Build

Be practical or creative, but limit your solution to a single source file, please.

There are now manifest files you can include in your submission so that your FizzBuzz solution will be run from the main script.

{
    "$schema": "../test_schema.json",
    "location": "/src/C",
    "nameShort": "C",
    "nameLong": "C",
    "buildCommand": "wsl",
    "buildCommandParameters": "./linux_build.sh",
    "buildCommandParametersArray": [ ],
    "executeCommand": "wsl",
    "executeCommandParameters": "",
    "executeCommandParameters": [ "./bin/linux/fizzbuzz" ],
    "preBuild": ""
}

• location - Relative path from the root of the project to the working directory of your solution.
• nameShort - A (very) short name for your solution with no spaces.
• nameLong - A descriptive name for your solution, which may have spaces.
• buildCommand - The command to execute in the shell to build your solution.
• buildCommandParameters - The parameters to pass to your buildCommand.
• executeCommand - The command to execute in the shell to run your solution.
• executeCommandParameters - The parameters to pass to your executeCommand.
• preBuild - A command to execute before building your solution.

Place this file in the first child directory of /src in your solution.

{
    "$schema": "../test_schema.json",
    "location": "/src/Ruby",
    "nameShort": "Ruby",
    "nameLong": "Ruby",
    "command": "wsl",
    "commandParmaters": "",
    "commandParametersArray": ["ruby", "./fizz_buzz.rb"],
    "preExecute": ""
}

• location - Relative path from the root of the project to the working directory of your solution.
• nameShort - A (very) short name for your solution with no spaces.
• nameLong - A descriptive name for your solution, which may have spaces.
• command - The command to execute in the shell to run your solution.
• commandParameters - The parameters to pass to your executeCommand.
• preExecute - A command to execute before running your solution.

Place this file in the first child directory of /src in your solution.

1 - Pattern-Lang is still concept only/

2 - Prints the sequence in PLA+ (single colour) on a Klipper printer (256×256 mm bed). Run from the Klipper console as FIZZBUZZ N=100. src/GCode/sim/simulate.py replays that call through Klippy batch mode and renders src/GCode/fizzbuzz_preview.png. run_all.ps1 skips the hash check: there is no host klipper command, and a toolpath cannot hash-match FizzBuzz.txt.

3 - Runs on a Homespring interpreter, such as hsrun from https://github.com/jneem/homespring (OCaml; build from source). The program is newline-sensitive, so it must keep LF line endings (a CRLF checkout makes it output nothing). run_all.ps1 skips it: hsrun is not on PATH, and hsrun prints a tree dump before the program output, so stdout cannot hash-match FizzBuzz.txt.