Sergey Teplyakov

Warn on StringBuilder.AppendFormat call without explicit {0} in it

1

For instance, the following code should be marked as dangerous: ```csharp var sb = new StringBuilder(); sb.AppendFormant($"Stuff {someStuff}"); ```

NoHeapAllocations

2

Add an attribute `NoHeapAllocation` and `AllowHeapAllocation`. User can put an attribute on assembly, class or member level. If the attribute is present than the member should follow some heap allocation...

Suggest a fix to switch to nameof if possible

1

For instance, in `new ArgumentException("argName")` to switch to `new ArgumentException(nameof(arg))`.

Async rules

8

- Warn on `async void` - Warn on `Task.Result`/`Task.Wait` prefer `Task.GetAwaiter().GetResult` because later will unwrap exception. Question: how to catch correct cases? - Warn on incorrect preconditions in async methods

Warn if a readonly struct is passed by 'ref'

1

Suggest to convert it to pass by 'in'.

I'm not sure that there is a case when this is fine. Fade an unused parameter.