chr

The toEnum method restricted to the type Char.
(chr) Translate the given integer to a character. (Note the result will depend on the character set of your database.)
Conversion from an integer to a character.
>>> prove $ \x -> 0 .<= x .&& x .< 256 .=> ord (chr x) .== x
Q.E.D.

>>> prove $ \x -> chr (ord x) .== x
Q.E.D.
Corresponds to the chr function.
A single Char fragment
A single Char fragment
Constructs a colour from the given Chromaticity and luminance.
Change the type used to represent the chromaticity coordinates.
Returns the CIE little x, little y, little z coordinates for the 2° standard (colourimetric) observer.
Returns the CIE little x coordinate for the 2° standard (colourimetric) observer.
Returns the CIE little y coordinate for the 2° standard (colourimetric) observer.
Returns the CIE little z coordinate for the 2° standard (colourimetric) observer.
Sort pages chronologically. Uses the same method as dateField for extracting the date.
A high-performance time library Chronos is a performance-oriented time library for Haskell, with a straightforward API. The main differences between this and the time library are:
  • Chronos uses machine integers where possible. This means that time-related arithmetic should be faster, with the drawback that the types are incapable of representing times that are very far in the future or the past (because Chronos provides nanosecond, rather than picosecond, resolution). For most users, this is not a hindrance.
  • Chronos provides ToJSON/FromJSON instances for serialisation.
  • Chronos provides Unbox instances for working with unboxed vectors.
  • Chronos provides Prim instances for working with byte arrays/primitive arrays.
  • Chronos uses normal non-overloaded haskell functions for encoding and decoding time. It provides attoparsec parsers for both Text and ByteString. Additionally, Chronos provides functions for encoding time to Text or ByteString. The http://hackage.haskell.org/package/time time> library accomplishes these with the Data.Time.Format module, which uses UNIX-style datetime format strings. The approach taken by Chronos is faster and catches more mistakes at compile time, at the cost of being less expressive.
Default Chrome settings. All Maybe fields are set to Nothing, no options are specified, and no extensions are used.
Server-side path to Chrome binary. If Nothing, use a sensible system-based default.
Version of the Chrome Webdriver server server to use for more information on chromedriver see https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver