5 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Mikael Kjellqvist commented  ·  January 26, 2012 16:11  ·  Flag as inappropriate  ·  Delete

  Wohoo, i hope the review goes well and the timeframe will be a short one :)

• Donna Malayeri (MSFT) commented  ·  November 28, 2011 14:08  ·  Flag as inappropriate  ·  Delete

  This would indeed be a nice feature, and we are considering it for a future release.

  However, please note that refactoring in F# (and similar languages) is a much harder problem than in OO languages, since it involves type inference and accounting for heavy use of higher order functions. Refactoring in Scala is also hard to implement (e.g., see http://devnet.jetbrains.net/message/5304630#5304630), and even "rename" in Java has problems! (http://dl.acm.org/citation.cfm?doid=1449955.1449787).

  This is not to say it cannot be done for F#, but it is definitely a tricky problem.

  Donna Malayeri - MSFT
  Visual Studio F# Program Manager

• igeta commented  ·  October 22, 2011 20:58  ·  Flag as inappropriate  ·  Delete

  Whether FP or OOP, it's really important to keep readable code.

• Anonymous commented  ·  October 22, 2011 10:53  ·  Flag as inappropriate  ·  Delete

  Refactorings are not that common in FP practice, mostly because functional composition depends more on type signature than name. So I don't think refactoring features are of top priority.

• mattias waldau commented  ·  October 21, 2011 05:29  ·  Flag as inappropriate  ·  Delete

  If you compare F# with Scala inside Intellij, there is a huge difference, Scala handles this much better.