I wrote halberd a while ago. It was mostly as an example of using the
haskell-names and haskell-packages packges (combined with
haskell-src-exts) that Roman Cheplyaka was working on at the time,
combined with a useful tool that I wanted for myself. The downside is
that haskell-packages doesn't use
I've found what I believe to be a regression in GHC 8 rc2 [1], and the
wiki says to yell if I want to bring it to the attention of GHC
developers. So this is me yelling, I guess :) I'm not sure if this bug
is important enough to be included, but I think it would be good for
someone to look at it an
I made an unofficial OS X build again [0]. I'd be happy to offer my
services to make an official build as well if people are interested
and know how to get this on the ghc download page.
Regards,
Erik
[0]
http://www.reddit.com/r/haskell/comments/2rims6/ghc_7100rc1_build_for_mac_os_x/
On Thu, M
On Fri, Feb 6, 2015 at 2:49 PM, Dominique Devriese
wrote:
> Agreed. For the idea to scale, good support for type-level
> programming with Integers/Strings/... is essential. Something else
> that would be useful is an unsatisfiable primitive constraint
> constructor `UnsatisfiableConstraint :: St
On Mon, Feb 2, 2015 at 9:37 AM, Herbert Valerio Riedel wrote:
> Hi Mark,
>
> On 2015-01-28 at 04:31:29 +0100, Mark Lentczner wrote:
>> I've just built a bindist under 10.10, but just normal not expressly llvm.
>> I'll test this in a bit then post it -- but might be sometime tomorrow
>> before it i
Hi George,
I've not tried compiling via llvm, but I have a working Mac GHC 7.10
build that I've been using, and haven't seen any of the other issues
you mentioned. I'm not sure what's recommended but I believe I'm using
clang (see output below). If you want to try my build, you can
download it at
I made a Mac OS X build. If people want to try it out, you can
download it from [0]. Let me know if you run into any issues.
Regards,
Erik
[0]
https://docs.google.com/a/silk.co/uc?id=0B5E6EvOcuE0nNFR4WUVNZzRtbGs&export=download
On Tue, Dec 23, 2014 at 3:36 PM, Austin Seipp wrote:
> We are ple
It seems to be building a very old cpphs (1.13) with a new version of
cabal. cpphs-1.13 has a top-level build-depends statement which isn't
allowed anymore: it should now be added to the library section, which
is what the error message tries to indicate.
Erik
On Thu, Jan 1, 2015 at 3:43 PM, Malco
On Mon, Oct 27, 2014 at 2:41 PM, Daniel Trstenjak
wrote:
>> There's a little bit of bikeshedding that needs to happen (e.g. is "hiding
>> (Foo
>> (..))" sufficient to hide the type Foo and not just its constructors), but
>> are
>> people +1 on this? I've frequently wanted this behavior.
>
> I wo
On Tue, Oct 21, 2014 at 4:55 PM, Mario Blažević wrote:
> On 14-10-21 07:14 AM, Erik Hesselink wrote:
>>
>> On Mon, Oct 20, 2014 at 11:57 PM, Mario Blažević
>> wrote:
>>> No, what I find much worse is a cabal update causing an error in
>>> a
>&g
On Mon, Oct 20, 2014 at 11:57 PM, Mario Blažević wrote:
> On 14-10-19 08:10 AM, Erik Hesselink wrote:
>>
>> Adding an explicit
>> import can suddenly cause type errors in completely unrelated places
>> (when it hides an implicit import and the new function is type
&
I feel that this extension, while looking tempting for writing code
from scratch, might hurt maintainability of code. Adding an explicit
import can suddenly cause type errors in completely unrelated places
(when it hides an implicit import and the new function is type
incorrect), or worse, can caus
I think most of the singletons stuff has been moved to the
'singletons' package [0].
Erik
[0] http://hackage.haskell.org/package/singletons
On Sat, Mar 15, 2014 at 6:26 PM, Henning Thielemann
wrote:
> Am 15.03.2014 18:13, schrieb adam vogt:
>>
>>
>> http://www.haskell.org/ghc/docs/7.8.1-rc2/htm
You can of course produce an infinite set of vacuous constraints using
the Symbol type (or any two non-equal types). For example, here you
could use:
Restrict a (a ': as) = ("Error" ~ "Oops! Tried to apply a restricted type!")
Erik
On Tue, Jan 14, 2014 at 2:56 PM, Merijn Verstraaten
wrote:
I'd like to repeat the suggestion to use cabal. It's very well suited
for simple programs. In addition, you get the ability to specify
dependencies, you can upload to hackage, etc.
Erik
On Mon, Jan 13, 2014 at 11:10 PM, Christian Brolin wrote:
> Thanks, but it is not a complicated build process.
I think that's a good idea. It was also suggested in a reddit thread
[0] a year ago, and it doesn't seem like that thread has any arguments
against it.
Erik
[0]
http://www.reddit.com/r/haskell/comments/10u7xr/ghc_head_now_features_agdalike_holes/c6gvy0r
On Mon, Jan 13, 2014 at 8:03 PM, migmit
I use HPC. It's really powerful in combination with tests, to see how
much of your code is covered. But I have also run into some of the
problems you mention, mostly to do with tix files.
Erik
On Thu, Nov 7, 2013 at 6:03 AM, Evan Laforge wrote:
> Is anyone out there using HPC? It seems like it
It looks like this instance is partial. Note that the record field 'y'
is also a partial function in plain Haskell. I've always considered
this a misfeature, but perhaps fixing that is outside the scope of
this proposal.
Erik
On Mon, Jun 24, 2013 at 4:40 PM, Oliver Charles wrote:
> On 06/24/2013
>
> When we discussed this last time (summarized by the link Pedro sent, I
> think) it came up that it might be nice to also
> have kind synonyms, which would be analogous to type synonyms, but one
> level up. The "natural" syntax for that would be to have a "type kind"
> declaration, but this se
t noticed that a very similar example (using Read) is
> described in the Haskell report's section on the monomorphism
> restriction.
>
> Roman
>
> * Erik Hesselink [2012-11-11 16:43:20+0100]
> > That's strange. Here, it only fails with both NoMonomorphismRestriction
>
That's strange. Here, it only fails with both NoMonomorphismRestriction and
NoMonoLocalBinds (which makes sense). I've tested on 7.4.1 and 7.6.1.
Erik
On Sun, Nov 11, 2012 at 3:54 PM, Roman Cheplyaka wrote:
> Apparently not — the code comilers with any of -XNoMonoLocalBinds and
> -XMonoLocalBi
On Wed, Apr 25, 2012 at 10:15, Yitzchak Gale wrote:
> The only reason I don't like using OverloadedStrings
> for typing string literals as Text and ByteString
> is that when you turn on OverloadedStrings, you turn
> it on for all types, not just Text and ByteString.
> I don't want to be forced to
On Tue, Apr 24, 2012 at 10:55, Michael Snoyman wrote:
> On Tue, Apr 24, 2012 at 11:36 AM, Erik Hesselink wrote:
>> On Tue, Apr 24, 2012 at 08:32, Michael Snoyman wrote:
>>> Here's a theoretically simple solution to the problem. How about
>>> adding a new
On Tue, Apr 24, 2012 at 08:32, Michael Snoyman wrote:
> Here's a theoretically simple solution to the problem. How about
> adding a new method to the IsString typeclass:
>
> isValidString :: String -> Bool
If you're going with this approach, why not evaluate the conversion
from String immediat
24 matches
Mail list logo
