{"id":1180,"date":"2014-01-25T14:48:06","date_gmt":"2014-01-25T14:48:06","guid":{"rendered":"http:\/\/putridparrot.com\/blog\/?p=1180"},"modified":"2014-01-25T14:50:39","modified_gmt":"2014-01-25T14:50:39","slug":"records-in-f","status":"publish","type":"post","link":"https:\/\/putridparrot.com\/blog\/records-in-f\/","title":{"rendered":"Records in F#"},"content":{"rendered":"

A far more comprehensive and frankly much better post on the subject of records can be found here<\/a>.<\/p>\n

However this post is an attempt to distil things down to some of the basics.<\/em><\/p>\n

Declaring a record type<\/strong><\/p>\n

Records can be thought of as a cross between a tuple with named fields and a specialised class. Basically the syntax is more in keeping with a class type but the specialisations are that, all properties are automatically exposed, you cannot define constructors as per classes and they have structural equality semantics<\/em> as opposed to a classes reference equality semantics<\/em>.<\/p>\n

Let’s declare a record type<\/p>\n

\r\ntype Person = { Name : string; Age : int }\r\n<\/pre>\n
Now to use this we simple write the following<\/p>\n
\r\nlet p = { Name = "Bob"; Age = 43 }\r\n<\/pre>\n
So as you see we do not need to actually use the type name Person<\/em> in the declaration (hence it appears similar to a tuple but with named properties and ofcourse using {…} instead of (…)). <\/p>\n
What if we declared the following<\/p>\n
\r\ntype Person = { Name : string; Age : int }\r\ntype Employee = { Name : string; Age : int }\r\n\r\nlet p = { Name = "Bob"; Age = 43 }\r\n<\/pre>\n
What type is p ?<\/p>\n
The value p will actually be assigned the type Employee as this was the last record declared. So we need a way to explicitly declare the type we want p to be (in the example above). This is done in the following way<\/p>\n
\r\nlet p = { Person.Name = "Bob"; Age = 43 }\r\n<\/pre>\n
Now p is of type Person.<\/p>\n
You will need to assign each of the named properties when creating a value of a record.<\/p>\n
To access the properties, we simply use dot notation and the property name, thus<\/p>\n
\r\nlet p = { Person.Name = "Bob"; Age = 43 }\r\n\r\nlet n = p.Name\r\n<\/pre>\n
Deconstructing a record<\/strong><\/p>\n
We can also deconstruct<\/em> a record to it’s constituent value as follows<\/p>\n
\r\nlet p = { Person.Name = "Bob"; Age = 43 }\r\n\r\nlet { Name = n; Age = a } = p\r\n<\/pre>\n
The above let<\/em> looks slightly odd in that we appear to be assigning the value n to Name whereas it’s actually the other way around in essence.<\/p>\n
Again, if you have more than one type which looks the same (as Person and Employee) you can again prefix the deconstruction to ensure the type is matched for example<\/p>\n
\r\nlet { Person.Name = n; Age = a } = p\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
A far more comprehensive and frankly much better post on the subject of records can be found here. However this post is an attempt to distil things down to some of the basics. Declaring a record type Records can be thought of as a cross between a tuple with named fields and a specialised class. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-1180","post","type-post","status-publish","format-standard","hentry","category-f"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1180","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=1180"}],"version-history":[{"count":10,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1180\/revisions"}],"predecessor-version":[{"id":1191,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1180\/revisions\/1191"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=1180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=1180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=1180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}