dotnet/roslyn

Scripting API: Avoid throwing and catching CompilationErrorException in Script.Build

Open

#5,949 opened on Oct 14, 2015

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-InteractiveInteractive-ScriptingLogichelp wanted

Description

Current impl is a quick workaround to get the APIs right.

Contributor guide

Tech stack
csharp
Domain
apideveloper experiencetooling
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C#Roslyn scripting API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the current implementation of Script.Build in the Roslyn source code (likely in Script.cs or ScriptBuilder.cs) to see how CompilationErrorException is thrown and caught. Look for comments on the issue for proposed alternatives, such as returning a Result type or using a different error reporting mechanism. The goal is to remove the exception handling and replace it with a more idiomatic pattern. Consider reviewing similar patterns in the codebase for guidance.