Question

So when ever im creating some properties in my F# code , as F# doesn’t support auto properties , as far as i know. I have to create backing fields and initialize them to null, which doesn’t seems right in functional programming terms. For e.g.

 let mutable albums : DbSet = null
 let mutable genres : DbSet = null


member x.Albums 
    with get() = albums
    and set(value) = albums <- value


member x.Genres
    with get() = genres
    and set (value) = genres <- value

Is there a better way of doing this ?. Many thanks for your suggestions.

Answer 1

F# does not support auto properties when you need a mutable property, but it supports a lightweight syntax when you need just a readonly property. If you’re writing some functional code, then using readonly properties might actually be more appropriate:

type Music(genres : DbSet, albums : DbSet) = 
  member x.Albums = albums
  member x.Genres = genres

This is essentially the same as records suggested by pad, but it may be more appropriate if you want to have better control over how the types look (and how they appear in C#, or for data-binding).

If DbSet is a mutable type, then you probably can just use the above type and initialize it just once (you’ll still be able to modify the DbSet values). If you want to change the DbSet value, you can add a method that returns a cloned object:

  member x.WithAlbums(newAlbums) = 
    Music(genres, newAlbums)

Using null or Unchecked.defaultOf<_> in F# is considered a very bad practice and you should always try to create fully initlized object. If the value may be missing, you can use option type to represent that, but then you have to always write handler for missing value, to make your program safe.