Reasons for using unsafe code

Question

What are some reasons for using unsafe code?

Direct access to the GC and better performance
The ability to throw types not-inherited from Exception, better performance, and the ability to write inline IL
The ability to write inline IL and better performance
Better performance and more control over unmanaged interop
More control over unmanaged interop, better performance, and the ability to write inline IL

It seems like a test question ? – Selman Genç Jan 23 '14 at 02:26 — Selman Genç, Jan 23 '14 at 02:26
Must be.. since most of it is wrong. – Simon Whitehead Jan 23 '14 at 02:26 — Simon Whitehead, Jan 23 '14 at 02:26
The closest I can see is option 4. – wonderful world Jan 24 '14 at 21:19 — wonderful world, Jan 24 '14 at 21:19

score 2 · Answer 1 · answered Jan 23 '14 at 02:32

2

Unsafe code is required if you need to use pointers which should be rare in .net.

From the docs here:

The use of pointers is rarely required in C#, but there are some situations that require them. As examples, using an unsafe context to allow pointers is warranted by the following cases:

Dealing with existing structures on disk

Advanced COM or Platform Invoke scenarios that involve structures with pointers in them

Performance-critical code

answered Jan 23 '14 at 02:32

bryanmac

38,941
11
91
99

If the pointers can deal with the unmanaged interop, the answer is 4. I don't think unsafe is used to write inline IL code. – wonderful world Jan 23 '14 at 02:37

Reasons for using unsafe code

1 Answers1