The F# Journal just published an article about data structures:
"F# is a versatile language that allows for many different ways in which to tackle a problem, since it encompasses functional, imperative and object-oriented programming techniques. However, the fact remains that it is a functional-first language, and as such, unless otherwise stated, it treats each computation as the evaluation of a mathematical function. Functions are seen as pure, meaning that they do not have side effects, either via memory or I/O actions - they do not alter the program's state. We're going to look at a standard problem which, using F#'s capabilities, can be solved by making use of some notion of state..."
To read this article and more, subscribe to The F# Journal today!
Background reading on the reference counting vs tracing garbage collection debate - Eight years ago I answered a question on Stack Overflow about the suitability of OCaml and Haskell for soft real-time work like visualization: "*for real-ti...
4 months ago