Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author | user:1234 user:me (yours) |
| Score | score:3 (3+) score:0 (none) |
| Answers | answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections | title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status | closed:yes duplicate:no migrated:no wiki:no |
| Types | is:question is:answer |
| Exclude | -[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with coding-style
Search options not deleted user 59429
Coding style is a set of guidelines that helps readability and understanding of the source code.
4 votes
When should I use a 2-property class over a pre-built structure like a KeyValuePair?
I would perhaps agree with Wilding here. I would suggest that the built-in types are often mechanism objects. KeyValuePair for example, is part of the mechanism of a dictionary and hash tables, help …
- 141