Every decision made in a public API will be a tradeoff between the strength of the abstraction and enabling the users. Giving your users the most options isn't necessarily bad, but it's certainly not the most important goal. What if you decide that the indexer isn't a vital part of the contract and the method could be better optimised if you implemented it with an iterator block and returned an IEnumerable? Can't change that without breaking all the users. That would be a direct violation of the Dependency Inversion principle.Īlso, the more specific the type, the weaker the abstraction your API provides.
You want to contract to your users that the returned collection has an indexer? IReadOnlyList or IList but never the concrete List or even worse, your own custom class implementing IList. By setting up a concrete return type you are commiting to using that concrete type and any change to that is breaking. You have to be very thoughtful about what you expose in a public API. If I were to take this advice literally and apply it everywhere, then I'd strongly disagree. I see you relaying the significance of knowledge and understanding - all quite agreeable.
Icollection code#
The vast majority of developers are going to get functional code done first - as that is what is expected of them in any particular task or criteria.Īt any rate, I don't see you providing or suggesting an actual solution as you raise this prominent issue. I don't disagree that understanding is crucial for writing efficient code, but I can't agree that efficient code is crucial (not to all the parties, and certainly not as it relates to revenue and earnings). Data structures, compilers, framework\technologies and runtime operation and performance considerations take time to understand - it's an incremental process we all go through. People have different levels of understanding on all matters. You're raising an issue that more related to why someone might ask this question then to post that responds to such a question. Read detailed descriptions of the rules here.
Icollection software#
Rule 2: No malicious, intentionally harmful, or piracy-related software.Rule 1: No job postings (For Hire and Hiring).Platform-specific Subreddits /r/windowsdev /r/AZURE /r/Xamarin /r/Unit圓D /r/WPDev
Related Subreddits /r/dotnet /r/azure /r/learncsharp /r/learnprogramming /r/programming /r/dailyprogrammer /r/programmingbuddies /r/cshighschoolersĪdditional. IDEs Visual Studio MonoDevelop (Windows/Mac/Linux) Rider (Windows/Mac/Linux)Īlternative Communities C# Discord Group C# Lemmy Community dotnet Lemmy Community Other Resources C# Yellow Book Dot Net Perls NET in 10 minutes C# Guide C# Language Reference C# Programing Guide C# Coding Conventions. Useful MSDN Resources A Tour of the C# Language Get started with. Getting Started C# Fundamentals: Development for Absolute Beginners
Information about Reddit's proposed API changes, the unprofessional conduct of the CEO, and their response to the community's concerns regarding 3rd party apps, moderator tools, anti-spam/anti-bot tools, and accessibility options that will be impacted can be found in the associated Wikipedia article: Īlternative C# communities available outside Reddit on Lemmy and Discord:Īll about the object-oriented programming language C#.
0 kommentar(er)
