Why This Matters

Cross-language conversion is a Copilot superpower — it understands both source and target idioms. This project builds the 'idiom mapping' skill that's essential when modernizing legacy code or migrating stacks.

Concept Explained

Pick a function in one language (JS). Convert it to another (Python). Verify behavior with a test in the target language. Apply target idioms (list comprehension in Python, not just for-loop translation).

How It Works

Paste the source snippet into Chat. Ask: 'convert this [JS] function to [Python], using idiomatic Python (list comprehensions, type hints)'. Verify by writing a test in the target language and running.

Step-by-Step Tutorial

1. Pick snippet

2. Convert with Copilot

3. Verify types

4. Write test in target

5. Document idioms

Real-World Example

A team migrating a JS analytics library to Python asked Copilot to convert 20 functions. Copilot translated for-loops to list comprehensions, callbacks to async/await, and JSON parsing to native Python. Each function was verified with a ported test. Migration took 2 days instead of 2 weeks.

Example Prompts / Commands / Code

// Source (JS):
function sumEven(nums) {
  return nums.filter(n => n % 2 === 0).reduce((a, b) => a + b, 0);
}

# Copilot converts to idiomatic Python:
def sum_even(nums: list[int]) -> int:
    """Sum the even numbers in the list."""
    return sum(n for n in nums if n % 2 == 0)

# Source (Python):
def find_users(users, active=True):
    return [u for u in users if u.active == active]

// Copilot converts to idiomatic Go:
func FindUsers(users []User, active bool) []User {
    var result []User
    for _, u := range users {
        if u.Active == active {
            result = append(result, u)
        }
    }
    return result
}

Common Mistakes

• Accepting literal translations instead of idiomatic ones.
• Not writing a test in the target language.
• Forgetting type differences (JS numbers vs Python int/float).
• Skipping edge case verification.

Best Practices

• Specify 'use idiomatic [target language]' in the prompt.
• Write a test in the target language to verify behavior.
• Check type mappings carefully.
• Verify edge cases match.
• Document idiom differences for the team.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Copilot for code conversion

Official References

• Refactoring with Copilot

Related lessons: BE-37, BE-38