F# Weekly #6, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #5Subscribe

Articles about using F# to implement Lisp

Jorge Tavares's avatarJorge Tavares Notes

I was looking for examples of Lisp implementations using F# and found these 3 interesting series of blog posts. You can find other posts about implementing Lisp or Scheme using F# but these were the ones I found more comprehensive and different enough to compare different implementations. Although these Lisp implementations are learning experiments and not for production use, it’s fun to see how they are implemented. The series are the following ones:

Tim Robinson’sLisp Compiler in F#:

  1. Introduction
  2. Parsing with fslex and fsyacc
  3. Expression trees and .NET methods
  4. http://www.partario.com/blog/2009/06/lisp-compiler-in-f-il-generation.html
  5. What’s next?

Ashley Nathan Feniello’sFScheme series:

  1. Scheme in F#
  2. Just ‘let’ Me Be Already!
  3. Lambda the Ultimate!
  4. Rinse and Recurse
  5. What ‘letrec’ Can’t Do
  6. What’s Lisp Without Lists?!
  7. No Wait, Macro the Ultimate!
  8. Oh, The Humanity!
  9. Language vs. Library
  10. Turning Your Brain Inside Out with Continuations
  11. Playing Dice with the Universe
  12. Functional I/O (or at least…

View original post 37 more words

F# Weekly #5, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #4Subscribe

Stormin’ F#

fwaris's avatarFaisal's space

Apache Storm is a scalable ‘stream computing’ platform that is fast gaining popularity. Hadoop and Storm can share the same cluster and the two complement each other well for different computing needs – batch for Hadoop and near-real-time for Storm.

Storm provides a macro architecture for executing ‘big data’ stream processing ‘topologies’. For example, one easily increase the parallelism of any node in the Storm topology to suit the performance requirements.

For streaming analytics, however, Storm does not offer much help out of the box. Often one has to write the needed analytic logic from scratch. Wouldn’t it be nice if one could use something like Reactive Extensions (Rx) within Storm components?

Luckily Nathan Marz – the original author of Storm – chose to enable Storm with multi-language support. While Storm itself is written in Clojure and Java, it implements a (relatively simple?) language-independent protocol that can be used with basically…

View original post 292 more words

F# Weekly #4, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #3Subscribe

F# Weekly #3, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #2Subscribe

F# Weekly #2, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #1Subscribe

FAKE Final Targets

Today I discovered a new (for me) FAKE feature called FinalTarget. I worked on integration with our new product ReportPortal (in beta right now) that collects and visualizes test results and faced a problem …

The integration process is the following:

  1. Start a new launch (test session) on the server
  2. Execute all tests: unit & integration tests (in my scenario).
  3. Close a launch on the server

As you see, I need to close a launch even in the case when tests failed. So I cannot stop an execution of build script directly on the failure. Unexpectedly, but FAKE provides an elegant solution for this scenario – FinalTarget (target that will be executed in any case if you activate it).

FAKE dependencies look like this in my script:

"Clean"
 ==> "RestorePackages"
 ==> "Build"
 =?> ("RP_StartNewLaunch", not <| hasBuildParam "skipTests")
 =?> ("RunUnitTests", not <| hasBuildParam "skipTests")
 =?> ("RunIntegrationTests", hasBuildParam "allTests")
 =?> ("RP_FinishLaunch", not <| hasBuildParam "skipTests")
 ==> "All"

Targets look like this:

Target "RP_StartNewLaunch" (fun _ ->
    ...
    ActivateFinalTarget "RP_FinishLaunch"
)

FinalTarget "RP_FinishLaunch" (fun _ ->
    ...
)

Target "RunUnitTests" (fun _ ->
    ...
)

Target "RunIntegrationTests" (fun _ ->
    ...
)

As you see, I defined FinalTarget instead of usual Target for “RP_FinishLaunch” and activated it on start of a new launch.

FAKE is awesome 😉

F# Weekly #1, 2015

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

Videos/Presentations/Courses

This week from F# Advent Calendar in English

This week from F# Advent Calendar in Japanese

Blogs

F# vNext News

New releases

That’s all for now. Have a great week.

Previous F# Weekly edition – #52Subscribe