⚡ Fast Olympic Coding ⚡

Once a mighty Competitive Programming plugin... Reborn with the powers of VSCode!

⚡ Overview

• 📜 Minimal and adaptive UI for maximized functionality and view utilization
• 🪲 Extension agnostic configuration for VSCode debugging UX with real-time inputs
• 🐞 Built-in stress tester as a first-class feature
• 🗨️ First-class support for interactive problems within both Judge and Stress Tester!
• 🛜 Support for Competitive Companion to gather problem inputs easily
• 👜 Insert file templates without leaving your code
• ⚡ BLAZINGLY FAST! Asynchronous design + optimizations = 99% spam proof!

📥 Fast Olympic Coding is available on Visual Studio Marketplace and Open VSX Registry

</> Setting Up

Provide run settings for the languages you use in runSettings.json at the root folder. Here is the default example configuration for C++, Python, and Java:

{
  ".cpp": {
    "compileCommand": ["g++", "${file}", "-o", "${fileDirname}/${fileBasenameNoExtension}"],
    "runCommand": ["${fileDirname}/${fileBasenameNoExtension}"]
  },
  ".py": {
    "runCommand": ["python", "${file}"]
  },
  ".java": {
    "compileCommand": ["javac", "${file}"],
    "runCommand": ["java", "-cp", "${fileDirname}", "${fileBasenameNoExtension}"]
  }
}

🔥 There are built-in default settings for C++, Python, Java, Go, Rust, JavaScript, TypeScript, Haskell, Ruby, Kotlin, and C#! Access them with Create runSettings.json command.

We can use VSCode's built-in variables which has the syntax of ${...} and will get resolved by the extension. ${defaultBuildTask} is not supported because it requires resolving the entire build configuration which is super slow!

💡 Since runSettings.json applies recursively to subdirectories, you can specialize parts of the configuration within specific directories. The extension traverses from the workspace root directory up to the file folder, merging the settings along the way in that order.

Example structure:

workspace/
├── runSettings.json          # Base settings for entire workspace
├── contests/
│   ├── runSettings.json      # Overrides for contests folder
│   └── codeforces/
│       ├── runSettings.json  # Overrides for codeforces folder
│       └── solution.cpp      # Uses merged settings from all 3 files

📜 Judge

Minimalistic UI from the old plugin have been reimagined to integrate VSCode's capabilities while maintaining the principle of maximum functionality within minimized space. The new UI experience is integrated into both Judge and Stress Tester views.

ℹ️ You can mix languages! For example, you can have a C++ solution and a Python interactor. This automatically applies to stress tester as well!

• Run, edit, hide, skip testcases, you name it!
• Hidden optimizations such as batched IO, truncating huge IO, and cached compilations.
• Icons and tooltips to save space while being self-explanatory
• Dedicated popup for compiler errors with color support
• ... and so much more!

🪲 Debugging

The extension typically attaches the debugger to an existing process, which allows custom inputs to be propagated to the program. However, each language has its own set of tooling. Adapt the commands as necessary!

🚨Please use ${debugPort} as the port for your debugging servers! The hand-picked port provides the following benefits:

1. The port is free
2. Detects when the debugging server fails to launch at the chosen port within a timeframe
3. Frees the port when error occurs

We also have ${debugPid} for PID of the process for other debugging configurations without a server.

‼️NOT ALL DEBUGGERS ARE EQUAL! Between debugging servers for the same language, they may not have the same set of features or work the same way! Same warning applies to VSCode debugger extensions!

{
  ".cpp": {
    // compile and run configurations from above...
    "debugCommand": ["gdbserver", ":${debugPort}", "${fileDirname}/${fileBasenameNoExtension}"],
    "debugAttachConfig": "GDB: Attach"
  }
}

{
  "configurations": [
    {
      "name": "GDB: Attach",
      "type": "cppdbg",
      "request": "launch",
      "program": "${fileDirname}/${fileBasenameNoExtension}",
      "MIMode": "gdb",
      "miDebuggerServerAddress": "localhost:${debugPort}",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": true
        }
      ],
      "cwd": "${workspaceFolder}"
    }
  ]
}

{
  ".py": {
    // compile and run configurations from above...
    "debugCommand": [
      "python",
      "-m",
      "debugpy",
      "--listen",
      "${debugPort}",
      "--wait-for-client",
      "${file}"
    ],
    "debugAttachConfig": "Python: Attach"
  }
}

{
  "configurations": [
    {
      "name": "Python: Attach",
      "type": "debugpy",
      "request": "attach",
      "connect": {
        "port": "${debugPort}"
      },
      "justMyCode": true
    }
  ]
}

{
  ".java": {
    // compile and run configurations from above...
    "debugCommand": [
      "java",
      "-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=${debugPort}",
      "-cp",
      "${fileDirname}",
      "${fileBasenameNoExtension}"
    ],
    "debugAttachConfig": "Java: Attach"
  }
}

{
  "configurations": [
    {
      "name": "Java: Attach",
      "type": "java",
      "request": "attach",
      "hostName": "localhost",
      "port": "${debugPort}"
    }
  ]
}

🐞 Stress Tester

We need both a file that outputs the correct solution and another that outputs a random input to both the current and correct solution. Additional information needs to be added to runSettings.json to tell the Stress Tester the names of these files. Here is the default example provided by the extension:

{
  "generatorFile": "${fileDirname}/${fileBasenameNoExtension}__Generator${fileExtname}",
  "goodSolutionFile": "${fileDirname}/${fileBasenameNoExtension}__Good${fileExtname}"
}

✨ The extension provides a 64-bit integer seed input for random number generators!

💡TIP: To stress test for Runtime Error instead of Wrong Answer, have the good solution be the same as the one to bruteforce against!

Demo of stress testing A+B!

🗨️ Interactive Mode

We need to tell the extension the name of our interactor file. Here is the default example provided by the extension:

{
  "interactorFile": "${fileDirname}/${fileBasenameNoExtension}__Interactor${fileExtname}"
}

✨ The interactor becomes the judge during stress test in interactive mode!

‼️FLUSH YOUR OUTPUTS! Even though this requirement has been stated in every interactive problem, it is still worth mentioning in case the files are interacting weirdly. FLUSHING SHOULD BE THE FIRST THING TO DOUBLE CHECK.

Due to the lack of standardization of interactor's results, I have taken the middle ground of various online judges' interactor's behavior. The exit code of the interactor will be used to determine the acceptance of the solution. Below lists the exit codes and the verdict:

Interactive testcases have a special badge to make them distinguishable. If there is no set secret, the testcase will ask you to provide one. This is a multi-line textbox because you have to give all the data in one go!

The convenient workflow of running interactive testcases!

Stress testing interactives is almost the same as regular stress testing!

🛜 Competitive Companion

Competitive Companion is a widely recognized browser plugin to conveniently fetch problem inputs. The plugin works with wide range of online judges and is actively maintained. Native support has been integrated directly into the extension for optimal workflow.

Using Competitive Companion to parse a CodeForces problem

We can parse an entire CodeForces Contest!

👜 Inserting Prewritten Code

• Add the root directory of the templates to the settings

Adding a tree reroot DP template without switching files

© Attributions

• FastOlympicCoding: The original Sublime Text package that inspired this extension 💖
• Flaticon: Icon for this extension 💖