Dear all,
I am pleased to announce the release on Hackage of a new Haskell ETL
Library, namely DBFunctor-0.1.0.0.
(“ETL” stands for Extract Transform and Load and is the standard technology
for accomplishing data management tasks in
Data Warehouses / Data Marts and in general for data migrations,
==
The 10th International Conference on Ambient Systems, Networks and Technologies
(ANT-2019)
Leuven, Belgium
April 29 - May 2, 2019
http://cs-conferences.acadiau.ca/ant-19/
=
Hi everyone,
Recently Neil Mitchell opened a pull request [1] proposing a single-line
change: Adding `{-# HLINT ... #-}` to the list of pragmas ignored by the
lexer. I'm a bit skeptical of this idea. Afterall, adding cases to the
lexer for every tool that wants a pragma seems quite unsustainable.
I rather agree.
We don't even need a convention do we? /Any/ comment in {- -} is ignored
by GHC /except/ {-# ... #-}. So tool users are free to pick whatever
convention they like to identify the stuff for their tool.
Simon
| -Original Message-
| From: ghc-devs On Behalf Of Ben Gamari
I like the suggestion of a flag. For any realistic compilation you
have to pass a large number of flags to GHC anyway. `stack`, `cabal`
or so on can choose to pass the additional flag by default if they
wish or make it more ergonomic to do so.
On Tue, Oct 16, 2018 at 7:58 PM Jared Weakly wrote:
>
Vladislav Zavialov writes:
> What about introducing -fno-warn-pragma=XXX? People who use HLint will
> add -fno-warn-pragma=HLINT to their build configuration.
>
A warning flag is an interesting way to deal with the issue. On the
other hand, it's not great from an ergonomic perspective; afterall,
