168 reputation
7
bio website itcrowd.be
location China
age 31
visits member for 1 year, 11 months
seen Dec 3 at 3:47

Utterly Insane developer


Feb
27
comment C# Classes instance members vs. enum
Hah... did not think of it that way... makes sense, will have to remember that
Feb
24
awarded  Revival
Feb
24
comment C# Classes instance members vs. enum
Great description, would just like to add that Enums can have behavior added to them using Extension methods, so adding GetHue() and GetSimilarityCoefficient() to an enum is possible.. it's just not used often
Feb
24
comment C# Classes instance members vs. enum
Yes, sorry about that. Updated it :-)
Feb
24
awarded  Editor
Feb
24
revised C# Classes instance members vs. enum
added 434 characters in body
Feb
23
awarded  Teacher
Feb
23
answered C# Classes instance members vs. enum
Jan
3
comment Use Queue<T> or stick to native f# lists
For reference, the book that is being referred to: cs.cmu.edu/~rwh/theses/okasaki.pdf
Jan
3
awarded  Scholar
Jan
3
comment Use Queue<T> or stick to native f# lists
Both answers have helped me understand the issue, but sadly I can only mark one as the answer, so +1 and thnx!
Jan
3
accepted Use Queue<T> or stick to native f# lists
Jan
2
awarded  Supporter
Jan
2
comment Use Queue<T> or stick to native f# lists
No, have no reason at all... it's a purely theoretical question
Jan
2
comment Use Queue<T> or stick to native f# lists
There's no real application involved, just playing to learn. In this case I'm writing a little game which greatly benefits from distinct unions and pattern matching... would be a huge pain to write it in c#. Let's say the queue contains something like cards, but where there are a lot more variations than 52 cards.
Jan
2
awarded  Student
Jan
2
asked Use Queue<T> or stick to native f# lists
Jan
2
awarded  Autobiographer