|
20h
|
|
awarded | Popular Question |
|
May
19 |
|
awarded | Famous Question |
|
May
18 |
|
awarded | Yearling |
|
May
17 |
|
answered | How to parse simple json object without extra libraries in c#? |
|
May
14 |
|
comment |
Copy key values from NameValueCollection to Generic Dictionary This answer should mention that NameValueCollections can have null keys, and this mismatch must be accounted for in converting to a dictionary, which has a non null key invariant
|
|
May
13 |
|
comment |
Finding Uppercase Character then Adding Space @cha - it is a language feature. what would you call it? |
|
May
13 |
|
answered | Nested Switch Statements: Architectural Design Issue |
|
May
13 |
|
revised |
Delete User Unit test added 1222 characters in body |
|
May
13 |
|
answered | Delete User Unit test |
|
May
10 |
|
answered | Finding Uppercase Character then Adding Space |
|
May
10 |
|
revised |
Using a class versus struct as a dictionary key edited tags |
|
May
10 |
|
comment |
Using a class versus struct as a dictionary key @280Z28, that's a good point - I updated my answer to address this. |
|
May
10 |
|
revised |
Using a class versus struct as a dictionary key added 1244 characters in body |
|
May
9 |
|
comment |
What is the most standard file format and notation for persisting expressive directed graphs? My problem with RDF is that you can represent a single semantic concept with infinite variations in syntax. This attribute of seems like a recipe for: (1) unintended redundancy; (2) arbitrary complexity; and, (3) terrible performance with any ontology of a significant-size. |
|
May
9 |
|
answered | Using a class versus struct as a dictionary key |
|
May
9 |
|
comment |
What is the most standard file format and notation for persisting expressive directed graphs? I appreciate the insight and this is one of the options I have been considering. I agree that Turtle syntax is the RDF flavor that is most consistent with my requirements, however, it's not clear from your answer why RDF is the best alternative, or even that you think it is. |
|
May
6 |
|
comment |
Nullable properties vs. Nullable local variables @Brian, I would go with something like new {}, but ideally it would be interned so you would always get the same reference. I'm sure Eric has given this a lot more though than I. I also think it would be really cool if you could configure defaults for interfaces and delegates through some sort of native IoC... it seems like the default for an unconfigured delegate would ideally do nothing, then return the default value for the return type (if not void). The same type of approach could be taken with interfaces. (this is obviously all impossible at this stage in the game, of course)
|
|
May
5 |
|
comment |
Nullable properties vs. Nullable local variables thank you. I've read a lot of criticism about how .NET addresses nulls in general (not just nullables). e.g. I'm sure you've heard it said that the fact that default(object) == null is an inherent flaw. Is there any place where you have specifically addressed this contention, and the underlying reason for the design decision? |
|
May
5 |
|
comment |
How to check if an object is nullable? @MarcGravell - so even if the particular T has an ==(T whatever, object obj)overload, then it wouldn't be called here? |
|
May
5 |
|
comment |
How to check if an object is nullable? i think your "obvious" clause should say ReferenceEquals(obj,null) , just to be safe |
