A C# library to write functional code - Part III - Records

Microsoft news and tips » A C# library to write functional code - Part III - Records

Mon, 21 Apr 2008 21:21:13 GMT

PingBack from http://microsoftnews.askpcdoc.com/?p=3525

Interesting Finds: 2008.04.22

gOODiDEA.NET — Tue, 22 Apr 2008 04:04:17 GMT

.NET RestLess - A Simple REST Framework ASP.NET AJAX Overview And Technical Tips A C# library to write

Interesting Finds: 2008.04.22

gOODiDEA — Tue, 22 Apr 2008 04:04:54 GMT

.NETRestLess-ASimpleRESTFrameworkASP.NETAJAXOverviewAndTechnicalTipsAC#libraryto...

Community Convergence XLIII

Charlie Calvert's Community Blog — Wed, 23 Apr 2008 23:58:14 GMT

Welcome to the forty-third issue of Community Convergence. The last few weeks have been consumed by the

re: A C# library to write functional code - Part III - Records

Eamon Nerbonne — Thu, 24 Apr 2008 12:11:28 GMT

By the way, there's another reason your hash-code algorithm is unwise: Assuming the component hash-codes are uniformly distributed over the integers from 0 to 2^32-1 (thus interpreting the signed integers as unsigned integers here, for simplicity), your will not be: a binary or never lowers the number of "on" bits; each bit of your result hash code has only a 25% chance to be off - which lowers the entropy of the overall hash code to be around 26 bits, as opposed to 32 bits.

Finally, tuples of tuples will hash particularly badly; and so will tuples with higher than 2-arity.

re: A C# library to write functional code - Part III - Records

lucabol — Thu, 24 Apr 2008 20:13:10 GMT

Eamon: you are right. It is bad. As I said before, I was lazy.

re: A C# library to write functional code - Part III - Records

ktmt — Fri, 25 Apr 2008 18:13:00 GMT

Wow, a little more and we'll finally have the easy-to-use record construct of Pascal in the 1980s. Just declare a Record type and you're set. I have (seriously) often wished for this in C# instead of cumbersome, separate struct or class def's.

re: A C# library to write functional code - Part III - Records

amiya — Thu, 08 May 2008 20:55:11 GMT

http://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.comhttp://www.amazingorissa.com

re: A C# library to write functional code - Part III - Records

TimNew — Tue, 20 May 2008 19:06:19 GMT

This's a really excellent introduction. I think I begin to know what the functional code is after reading your posts and code. But I have some questions about this:

For the GetHashCode(), why don't you try "xor" other than "or"? I think "xor" will get a better job than the "or"~

For something about all the code, and I found TypeUnion<T> is really useless! Since I'll never have the change to use a member union!

Luca Bolognese's WebLog : A C# library to write functional code - Part III - Records

pligg.com — Sat, 24 May 2008 01:55:17 GMT

Previous posts: Part I - Background Part II - Tuples Now that we know what Tuples are, we can start talking about Record, as they use a derivative of Tuples under the cover. But first, what is a record? Well, in C# parlance a Record is a sort of immutabl

The Quest for Quick-and-Easy Class-Based Immutable Value Objects in C# - Part 1: Introduction

adamjcooper.com/blog — Tue, 03 Jun 2008 22:38:39 GMT

The Quest for Quick-and-Easy Class-Based Immutable Value Objects in C# - Part 1: Introduction

The Quest for Quick-and-Easy Immutable Value Objects in C#

adamjcooper.com/blog — Wed, 04 Jun 2008 00:00:02 GMT

The Quest for Quick-and-Easy Immutable Value Objects in C#

A C# library to write functional code - Part V - The Match operator

Luca Bolognese's WebLog — Tue, 15 Jul 2008 12:46:24 GMT

Other posts in the series: Part I - Background Part II - Tuples Part III - Records Part IV - Type Unions