See the Fay web site for documentation.
A proper subset of Haskell that compiles to JavaScript, Fay is a small programming language which has the following properties:
- A proper syntactic and semantic subset of Haskell
- Statically typed
- Lazy
- Pure by default
- Compiles to JavaScript
- Has fundamental data types (Double, String, etc.) based upon what JS can support
- Outputs minifier-aware code for small compressed size
- Has a trivial foreign function interface to JavaScript
- Supports cabal installation of Fay packages.
To install:
$ cabal install fay fay-base
Or download and unpack:
$ cabal unpack fay
$ cd fay
$ cabal unpack fay-base
$ cabal install . fay-base/
To run tests from within this directory (you need nodejs installed):
$ fay-tests
To generate documentation (from within this directory):
$ fay-docs
Try it out (make sure you have fay-base package installed, or you'll get an error about missing fay-base):
$ fay examples/console.hs
$ node examples/console.js
Hello, World!
Cabal-dev also works:
$ cabal-dev install
Given that cabal-dev is installed in a specific dir, you'll wanna install fay-base in the same dir:
$ cabal-dev install fay-base
Then run the normal stuff:
$ cabal-dev/bin/fay-tests
$ cabal-dev/bin/fay-docs
$ cabal-dev/bin/fay --no-ghc examples/console.hs
$ node examples/console.js
Hello, World!
If you only installed with cabal-dev then you will probably get a 'no package fay' error from GHC, so you can tell it where to get the package from with an environment variable:
HASKELL_PACKAGE_SANDBOX=cabal-dev/packages-7.4.1.conf cabal-dev/bin/fay examples/alert.hs
fay-base contains Fay's standard library and is needed in order to use the compiler.
Here's an example of a FFI declaration:
max :: Double -> Double -> Double
max = ffi "Math.round(%1,%2)"
%1,%2,..
corresponds to the arguments you specify in the type.
Be careful when declaring FFI types because Fay can not verify that they are correct.
A FFI function often has side effects, use the Fay
monad to represent this:
unixTime :: Fay Int
unixTime = ffi "new Date().getTime()"
You can only use point free style in FFI functions, foo x = ffi "..." x
is not allowed.
Usually you want to access some JavaScript global it's a good idea to always use global access so that a local fay binding won't interfere:
alert :: String -> Fay ()
alert :: ffi "window.alert(%1)"
If you want to access window
(browser) or global
(nodejs) you can do:
log :: String -> Fay ()
log = ffi "(function () { this.console.log(%1); }).call()"
For Google Closure's advanced optimizations you need to use string access to properties:
jQuery :: String -> Fay JQuery
jQuery = ffi "window['jQuery']"
You can serialize to and from records automatically like this:
data Con = Con Double String
printCon :: Fay ()
printCon = print (Con 1 "str") -- Will output { instance : 'Con', slot1 : 1, slot2 : 'str' }
data Rec = Rec { a :: Double, b :: String }
printRec :: Fay ()
printRec = print (Rec { a = 1, b = "str" }) -- Will output { instance : 'Rec', a : 1, b : 'str' }
getRec :: Fay Rec
getRec = ffi "{ instance : 'Rec', a : 1, b : 'str' }" -- Gives you Rec { a = 1, b = "str" }
Here are the rules for serialization. All serialization is based on the type you specify at the ffi declaration, e.g.:
foo :: Int -> String
foo = ffi "JSON.stringify(%1)"
The rules are simple:
- Concrete type, e.g.
String
,Maybe Int
: yes, will be de/serialized. - Polymorphic, e.g.
a
,Maybe a
: will not be touched.
There are two helpers for turning on/off serialization for the above:
Ptr Foo
: will not be touched.Automatic a
: will attempt to automatically serialize thea
at runtime.
There are two utility types for interfacing with JS APIs:
Nullable a
:Null
will be serialized tonull
.Defined a
:Undefined
will be serialized toundefined
, and will be ommitted from serialized objects e.g.Foo Undefined
โ{"instance":"Foo"}
.
When recompiling fay you need to recompile fay-base as well. It might best to do
fay$ git clone git://github.com/faylang/fay-base.git
fay$ cabal install . fay-base/
If you intend on submitting a pull request, whichever branch you choose to submit a pull request on, please ensure that it is properly rebased against master. This will ensure that the merge is clean and that you have checked that your contribution still works against the recent master. A typical workflow might be:
Set up a remote that you can use to track the main repository:
$ git remote add fay git://github.com/faylang/fay.git
Start our topic branch:
$ git branch my-topic-branch
Hack hack hack! Once changes committed, run git pull on master and try to rebase onto it to check whether your work is out of date.
$ git commit -a -m "My topic done."
$ git fetch fay
$ git rebase fay/master -i
Install with cabal install
and run fay-tests
. If there are
no warnings and all tests pass, move on.
If there are any conflicts, resolve them. Install and run fay-tests
again. Push changes to your Github fork:
$ git push origin my-topic-branch
Make a pull request on Github for my-topic-branch. Pull request gets merged in. Pull from the official Github remote:
$ git pull haskell master
Delete your topic branch:
$ git branch -D my-topic-branch
I'm all done!