Presenter: John Hughes
Research and publish the best content.
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
Functional programming
13.5K views |
+0 today
 Your new post is loading...
Your new post is loading...
Scoop.it!
Mark Seemann uses F# to demonstrate how to use functional design with TDD to remove the need for Mock objects. 
Scoop.it!
Domain modeling in F# is significantly easier and safer than with the
Scoop.it!
This post summaries the seven ineffective coding habits that Kevlin Henney outlined in his talk and how, in opinion and experience, F# helps prevent.
Scoop.it!
I'd like to share my experience with functional programming in this article. I feel like I've learned more in the...
Scoop.it!
This is part 8 of Categories for Programmers. Previously: Functors. See the Table of Contents. Now that you know what a functor is, and have seen a few examples, let's see how we can build larger f...
|
Scoop.it!
This article is the third in the "Running your own DNS Resolver with MirageOS" series. In the first part, we used the ocaml-dns library to lookup the hostname corresponding with an IP address using...
Scoop.it!
One of my goals this year is to learn a new programming language. This language should use a programming style different than what I am familiar with (currently C# and Javascript). As I am settled in the .net space I...
Scoop.it!
Three weeks ago I wrote about my experiences trying out Akka.NET. I had assembled a small working Akka.NET example application written in F# using the information I was able to find on the subject. My first attempt however...
Scoop.it!
Type Providers are an essential element for F#’s extensibility model, but creating new ones can be a chore. Dave Fancher shows how to take the tedium out authoring Type Providers using some simple inline factory methods.
Scoop.it!
Phil Trelford describes and demonstrates areas where F# excels, such as domain modeling, computation and concurrency.
Scoop.it!
Over the last few years, I created or contributed to a number of libraries. In this blog post (or perhaps a series), I'll share some of the things I learned when trying to answer the question: What should a good library look like? I'll start by looking at a library design pattern that I call 'levels of abstraction'.
Scoop.it!
The project page on OpenHub.net for FsSql. Functional wrapper around ADO.NET for F#
Scoop.it!
As I talked about last week, I was looking at different ways of using the Entity Framework type provider to map to my domain model. While I was working on the process, Ross McKinley saw...
Scoop.it!
I like Haskell because it lets me live inside my world. There are a lot of special worlds out there! And Haskell lets me stay in those worlds, and use all of the tools I normally have when I’m not there. I get to transform normal tools into tools that work in my world. (This post is meant to be approachable by people unfamiliar with Haskell! That being said, if there is a concept you don’t understand, feel free to leave a comment, tweet me, stop by on irc at freenode’s #haskell, or give Learn Yo
|
