Back to Questions
1.1k
views4
comments
compare F# version 1.9.6.2 and 1.9.6.16
f#

I found that there are many functions between 1.9.6.2 and 1.9.6.16 version are different, such as List.fold_left and List.foldBack, I am wondering why F# team does in this way?? Does this mean in the future, some functions will be continuously changed in the new version?? if so, it is better not to use F# now, or else, you can imangine, you have to replace the functions in order to adapt to new version. this is really abnormal.

.

Breaking changes and renames are very common for "pre-Beta" products. (If anything F# is abnormal in that it is already so stable - almost all the 'breaking' changes at the source code level from 1.9.6.2 to 1.9.6.16 are merely deprecation warnings saying we renamed a library function. I think if you pick most any other product, you're likely to find vastly more significant changes from CTP to Beta1.) There will continue to be some changes up until F# is released along with VS2010, but we are definitely converging on the final form of the language and libraries.

By on 5/24/2009 9:35 AM ()

Hi,

Let's accept breaking changes with good grace and urge the FSharp team to be a bold as they can be in getting the language and libraries as concise, powerful and compliant as they can before the first official release.

regards,

Danny

By on 5/24/2009 12:32 PM ()

Indeed. I'd find it abnormal if the new release would _not_ have breaking changes. There is no point in trying to maintain backward compatibility between beta releases - that burden will weigh in heavy enough when the first production release is out the door.Besides, the kind of changes you mention are simply name changes, nothing significant. I didn't have to rewrite any code, just search and replace some stuff.

By on 5/25/2009 2:51 AM ()

The places I had changes were mainly places where I was relying on the F# compiler being lose on things. For instance, I think they tightened up type extensions a bit -- you have to match the generics used in the original type exactly. (Which has been a bit of a problem for certain C# uses of generics.) But it's better than before, I think, because at least it restricts you from writing compiling-but-incorrect code!

By on 5/25/2009 10:34 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper