dotnet/roslyn

Allow unsafe code in Interactive Window

Open

#48,631 opened on Oct 15, 2020

View on GitHub
 (8 comments) (5 reactions) (0 assignees)C# (4,257 forks)batch import
Area-InteractiveConcept-Continuous ImprovementInteractive-ScriptingIDEhelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Currently the code is compiled in safe context, which makes experimenting with (function) pointers awkward (all unsafe code must be wrapped in unsafe { }).

We should enable unsafe context by default.

In addition, we could add #unsafe (on|off|enable|disable) host command that toggles the setting.

Contributor guide

Research direction
Investigate how the Interactive Window compiles code and modify the compilation options to allow unsafe code by default. Also implement a #unsafe host command to toggle the setting.
Tech stack
csharp
Domain
developer experience
Issue type
Feature
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NET
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70