.NET Fiddle adds F#
dotnetfiddle.net
.NET Fiddle adds F#
1–10 of 72 posts
Re: .NET Fiddle adds F#
#2I found F# to be rather neat. This is a great way to see for yourself.
Re: .NET Fiddle adds F#
#3Can anyone comment how F# compares to other functional languages? Just curious.
Re: .NET Fiddle adds F#
#4Can anyone comment how F# compares to other functional languages? Just curious.
learn haskell because it's harder.
Re: .NET Fiddle adds F#
#5Can anyone comment how F# compares to other functional languages? Just curious.
F# is very un-functional in many ways. Immutable variables are the default but mutable variables are made with just the "mutable" keyword. There are also lots of imperative control structures, like while, and for. Those two combined means that imperative algorithims typically have two distinct translations into F#.
First you can translate it literally, where F# looks like a slightly more verbose version of Python. Second you can exploit all the functional features of F#, and using immutable variables, recursion and pattern matching.
F# also has extensive support for OOP, and uses it where OCaml-ers might use modules or functors.
In that way, F# can be a sort-of stepping stone between the imperative, OOP C# to more functional features of F#.
Re: .NET Fiddle adds F#
#6Can anyone comment how F# compares to other functional languages? Just curious.
F# is very un-functional in many ways. Immutable variables are the default but mutable variables are made with just the "mutable" keyword. There are also lots of imperative control structures, like while, and for. Those two combined means that imperative algorithims typically have two distinct translations into F#. First you can translate it literally, where F# looks like a slightly more verbose version of Python. Se…
The idea is that it is a functional first programming language, but allows you to use imperative or OO styles when the problem suits it.
Re: .NET Fiddle adds F#
#7Small interruption. Looks like scaling to 2 servers on Azure to handle extra traffic crashed the original one.
Re: .NET Fiddle adds F#
#8Earlier quoted context omitted.
F# is very un-functional in many ways. Immutable variables are the default but mutable variables are made with just the "mutable" keyword. There are also lots of imperative control structures, like while, and for. Those two combined means that imperative algorithims typically have two distinct translations into F#. First you can translate it literally, where F# looks like a slightly more verbose version of Python. Se…
The idea is that it is a functional first programming language, but allows you to use imperative or OO styles when the problem suits it.
The OOP and imperative capabilities also make it easier for people coming from this kind of programming style to learn F#, such as myself.
At first you write imperative F# to get used to the language and it's lack of verbose signs such as (, ; etc and hopefully you will be able to write more idiomatic/functional F# as your skill improves.
Re: .NET Fiddle adds F#
#9Can anyone comment how F# compares to other functional languages? Just curious.
F# is very un-functional in many ways. Immutable variables are the default but mutable variables are made with just the "mutable" keyword. There are also lots of imperative control structures, like while, and for. Those two combined means that imperative algorithims typically have two distinct translations into F#. First you can translate it literally, where F# looks like a slightly more verbose version of Python. Se…
Un-functional might be a bit misleading for an ML-based, default immutable language. Impure might be slightly more accurate.
Having seen F# written by C# coders who've just learnt the syntax, and haskell programmers who are having to work in a .net environment, I'd say F# does a fairly good job of supporting both. It does make some trade offs to allow easy interop with the rest of the .net world (it's type system is much less powerful than Haskell, Scala or (especially) Idris) but depending on your environment that can be out weighed by the massive scale of the .net ecosystem, easy interop with your existing .net code and very, very good tooling.
Re: .NET Fiddle adds F#
#10Small interruption. Looks like scaling to 2 servers on Azure to handle extra traffic crashed the original one.
Azure will reset your VMs when you update their configuration. Normally this involves a rolling reset but as you only have one instance this was not possible.