I don't see sharp anymore, ...
-
... but the C# compiler doesn't complain, so it's likely valid code:
Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> MyTypes = new Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>>();
Why should you define a class when you can do the job with built-in types? :^)
-
... but the C# compiler doesn't complain, so it's likely valid code:
Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> MyTypes = new Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>>();
Why should you define a class when you can do the job with built-in types? :^)
Quick, get him back to front end.
Wrong is evil and must be defeated. - Jeff Ello
-
... but the C# compiler doesn't complain, so it's likely valid code:
Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> MyTypes = new Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>>();
Why should you define a class when you can do the job with built-in types? :^)
-
... but the C# compiler doesn't complain, so it's likely valid code:
Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> MyTypes = new Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>>();
Why should you define a class when you can do the job with built-in types? :^)
I've...err....done something like that before. I'm not proud of it, and in my defense I was about 10 min from presentation and found a bug, but still....
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
Oh dear, shame on me! What prevented me from seeing that - the code or my presbyopia? :-\
-
Oh dear, shame on me! What prevented me from seeing that - the code or my presbyopia? :-\
-
... but the C# compiler doesn't complain, so it's likely valid code:
Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> MyTypes = new Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>>();
Why should you define a class when you can do the job with built-in types? :^)
Nothing wrong with that, but maybe use an alias instead. Would you prefer:
class MyTypeCollection : Dictionary<string, List<Tuple<string, DateTime, List<MyType>>>> {}