New Unsafe errors have awkward phrasing

[agocke]

New:

ld) 'MathF.Cosh(float)' must be used in an unsafe context because it is marked as 'RequiresUnsafe' or 'extern'

Old:

Pointers and fixed size buffers may only be used in an unsafe context

I think the first phrasing is awkward and the second is better. I also don’t like “marked RequiresUnsafe or extern”

1. We don’t use RequiresUnsafe anymore
2. Within an assembly we know which it is and could just say that. For assembly references we could keep the current wording or just “unsafe”, since they all look the same.

[jjonescz]

1. We don’t use RequiresUnsafe anymore

You are using an outdated compiler then; the error message is now "{0} must be used in an unsafe context because it is marked as 'unsafe' or 'extern'"

2. Within an assembly we know which it is and could just say that. For assembly references we could keep the current wording or just “unsafe”, since they all look the same.

Can you clarify what are you actually suggesting instead of "{0} must be used in an unsafe context because it is marked as 'unsafe' or 'extern'"?