Code Editor

CodePlanet's built-in code editor provides a powerful, browser-based coding environment for solving problems and experimenting with code.

Editor Overview

The code editor is powered by Monaco Editor (the same engine behind VS Code), giving you a familiar, production-grade editing experience directly in the browser.

Core Features

Supported Languages

The code editor and execution engine support the following languages:

Keyboard Shortcuts

Editing

Execution

Navigation

Running Code

Quick Execution

1. Write your code in the editor
2. Select the correct language from the dropdown
3. (Optional) Add input in the stdin panel
4. Click Run or press Ctrl + Enter
5. View output in the Output panel below

Problem Submissions

When solving a problem:

1. Read the problem statement and constraints
2. Write your solution in the editor
3. Click Run to test against sample test cases
4. Click Submit to test against all hidden test cases
5. View detailed results: pass/fail per test case, runtime, and memory usage

Execution Limits

Input/Output

Standard Input

For problems that require reading from stdin, provide your input in the Input panel. Each line of input corresponds to one read operation.

Example (Python):

# Input panel contains:
# 5
# 1 2 3 4 5
 
n = int(input())
nums = list(map(int, input().split()))
print(sum(nums))
# Output: 15

Standard Output

Your program's output appears in the Output panel. Output is compared against expected results during submissions — whitespace is normalized (leading/trailing whitespace and trailing newlines are trimmed).

Error Handling

The editor provides clear feedback for common issues:

• Compilation Errors — Shown inline with line numbers and error messages
• Runtime Errors — Stack traces displayed in the output panel
• Time Limit Exceeded (TLE) — Your code exceeded the maximum allowed runtime
• Memory Limit Exceeded (MLE) — Your code used too much memory

Tips

• Test locally first: Use the Run button with sample inputs before submitting
• Check edge cases: Empty arrays, single elements, maximum constraints
• Read the constraints: They hint at the expected time complexity
• Use the language you know best: Don't switch languages mid-problem unless necessary