Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 923691
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T19:13:57+00:00 2026-05-15T19:13:57+00:00

First, I acknowledge the possibility that this question could be a duplicate; just let

  • 0

First, I acknowledge the possibility that this question could be a duplicate; just let me know.

I’m curious what the general “best practice” is for those situations when mutability is desired. F# seems to offer two facilities for this: the let mutable binding, which seems to work like variables in “most” languages, and the reference cell (created with the ref function) that requires explicit dereferencing to use.

There are a couple of cases where one is “forced” into one or the other: .NET interop tends to use mutable with <-, and in workflow computations one must use ref with :=. So those cases are pretty clear-cut, but I’m curious what to do when creating my own mutable variables outside of those scenarios. What advantage does one style have over the other? (Perhaps further insight into the implementation would help.)

Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T19:13:57+00:00Added an answer on May 15, 2026 at 7:13 pm

    I can only support what gradbot said – when I need mutation, I prefer let mutable.

    Regarding the implementation and differences between the two – ref cells are essentially implemented by a very simple record that contains a mutable record field. You could write them easily yourself:

    type ref<'T> =  // '
      { mutable value : 'T } // '
    
    // the ref function, ! and := operators look like this:
    let (!) (a:ref<_>) = a.value
    let (:=) (a:ref<_>) v = a.value <- v
    let ref v = { value = v }
    

    A notable difference between the two approaches is that let mutable stores the mutable value on the stack (as a mutable variable in C#) while ref stores the mutable value in a field of a heap-allocated record. This may have some impact on the performance, but I don’t have any numbers…

    Thanks to this, mutable values that use ref can be aliased – meaning that you can create two values that reference the same mutable value:

    let a = ref 5  // allocates a new record on the heap
    let b = a      // b references the same record
    b := 10        // modifies the value of 'a' as well!
    
    let mutable a = 5 // mutable value on the stack
    let mutable b = a // new mutable value initialized to current value of 'a'
    b <- 10           // modifies the value of 'b' only!
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.