`throw new NotImplementedException()` in shipped code. The member compiles; the caller fails at runtime.
Each example shows the exact code shape the rule is looking for, then the smallest version that keeps the intent without hiding risk or adding noise.
public class S3Storage : IStorage
{
public Task UploadAsync(Blob blob) => _client.PutAsync(blob);
public Task DeleteAsync(string key)
{
throw new NotImplementedException();
}
}Deterministic line match on masked source: flags `throw new NotImplementedException(` outside comments and strings.
public class S3Storage : IStorage
{
public Task UploadAsync(Blob blob) => _client.PutAsync(blob);
public Task DeleteAsync(string key) => _client.DeleteObjectAsync(_bucket, key);
}Implement the member. If it is intentionally unsupported, throw `NotSupportedException`; if the work is deferred, track it in a ticket rather than shipping the stub.
IDE scaffolding and agents generate members with this placeholder body to satisfy an interface, and the stub survives because nothing fails until that path runs.
ai-slop/csharp-not-implemented
ai-slop
Deterministic line match on masked source: flags `throw new NotImplementedException(` outside comments and strings.
Test files and generated files are not flagged. `NotSupportedException`, the conventional signal for an intentionally unsupported member, is not matched.
Part of aislop's C# rule set. First-class C# support, including C#-specific AI-slop rules, arrived in aislop v0.14.1.