This is definitely straying into footgun territory.
this post was submitted on 09 Oct 2025
8 points (100.0% liked)
C Sharp
1754 readers
1 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 2 years ago
MODERATORS
No moreso than extension methods already did, I think. The only real concern is naming conflicts, which are generally an immediate compiler error that's easily resolved. Certainly a little more likely for something like an indexer, that doesn't HAVE a name, but what are the odds, really, of not only wanting to add an indexer to a type where it makes sense to have one and that type doesn't have one already, but also that there would be MULTIPLE different conflicting ways for that to make sense?
Personally, I think this has been a long time coming.