On Mon, Jul 27, 2020 at 08:57:12PM +, Richard Eisenberg wrote:
> On the other hand, we could imagine a dedicated GHC API volunteer who
> maintains the API on top of the shifting sands of GHC.
Looking at other compilers that have been successful in having a stable
API - like clang with the
Hi Herbert,
On Thu, Mar 28, 2019 at 08:33:41PM +0100, Herbert Valerio Riedel wrote:
> I'm a programmer. I'm very used to devel tooling I'm expected to invoke
> as a programmer to be affected by what's in scope as a function of the CWD,
> e.g. `cabal`, `git`, `make` to name a few.
I think the
Hi Wren,
Incidentally, if we really want to pursue the get rid of CPP by
building it into the GHC distro...
In recent years there've been a number of papers on variational
lambda-calculi[1] which essentially serve to embed flag-based
preprocessor conditionals directly into the language
Hi Simon,
It is tantalising to me that something so critical has been so long delayed.
It’d be fantastic if it was done this summer.
I'm just wondering what kind of negative side effects it might have.
Sure, it will - most likely - make installing of cabal packages a lot
easier, especially
Hi Simon,
On Mon, May 11, 2015 at 11:27:58AM +, Simon Peyton Jones wrote:
Well, no one is actually suggesting that!
But you're just getting it automatically if you're depending e.g.
on the libraries A and B, and A depends on C 1.0 and B depends on C 2.0.
Currently you can't build this
On Mon, May 11, 2015 at 05:42:00PM +0200, Boespflug, Mathieu wrote:
In your example, an app wouldn't get both C 1.0 and 2.0. It would get
whichever
one of those fits the constraints of both A and B, or the build will fail if
no
such C exists.
Thanks for the clarification! I thought this
Hi Konstantine,
let bar' = bar{foo{val}=10}
If you're inside a record context you might just have something like:
let bar' = bar { foo.val = 10 }
and
let val = bar { foo.val }
or even
let bar' = bar { foo.val %= someFunction }
This just seems to be some kind of syntactic sugar,
Hi Simon,
Now I want to rebase to clean up. Can I just do a local rebase and then git
push? Nothing special about the push?
You will most likely need to add a '--force' to your push, to overwrite
the branch in the remote repo.
Greetings,
Daniel
Right! I'm on branch wip/new-flatten-skolems-Oct14, so
git push --force
should push just that branch right?
If I want to be super-safe, and say push only this branch would I say
git push --force HEAD
or
git push --force wip/new-flatten-skolems-Oct14
or something
Newer versions of git have this now as their default behaviour, but
I'm not quite sure which git version was the first one.
Ok, it's starting with git 2.0.
Greetings,
Daniel
___
ghc-devs mailing list
ghc-devs@haskell.org
Hi Nicolas,
So, if 1.4.x, 1.5.x, 1.6.x and 1.7.x are 'supported' versions, and some
bug is found in 1.6.2, but turns out to be introduced in 1.5.1, we fix
the bug in the 1.5 branch.
Then, if the bugfix is important enough, we merge 1.4 in 1.5 (which can
be a no-op), 1.5 in 1.6, and 1.6
On Thu, Sep 25, 2014 at 12:03:13PM +0200, Herbert Valerio Riedel wrote:
I'd just like to point out, that lists are something that you may want
to tweak regularily in code (while tuple are rather fixed-size entities whose
size is extended less frequently)
Consider the following JSON example:
On Wed, Sep 24, 2014 at 02:50:22AM -0400, Edward Kmett wrote:
.. whereas I've adopted prefixed comma-lists in Haskell to avoid the
need for an extension like this one, so it'd be quite a shift in my
programming style to get to where this helps me.
That also lets me somehow question the whole
On Wed, Sep 24, 2014 at 10:48:40AM +0200, Andreas Abel wrote:
[,a,b,] is [a,b]
(,a,b,) is a tuple section
However, I never felt like having list sections would see abundant
usage. Thus, this discrepancy is ok, imho.
I've somehow to disagree, because I like Haskell especially because
On Tue, Jul 29, 2014 at 12:02:19PM +0200, Johan Tibell wrote:
What's the rationale to not require
{-# OVERLAPPING Show [Char] #-}
here? Perhaps it's too annoying to have to repeat the types?
This one might be written at the top of the file, so it would be easier
to overlook it, than
On Mon, Apr 07, 2014 at 09:27:32PM +0700, Kim-Ee Yeoh wrote:
What if we replace captcha with a short, static question, the web form
equivalent of a secret handshake? And give it enough weighting to override
akismet?
E.g.
* What is Haskell's middle name?
* What is SPJ's middle name?
Hello,
I don't know if I'm the only one struggeling with this GHC error message
on type mismatches or it's because I'm not a full time Haskeller, or
because I'm not a native english speaker.
Couldn't match type `A' with `B´
Expected type: B
Actual type: A
My problem is with
Hi Mark,
On Sun, Nov 03, 2013 at 03:01:32PM -0800, Mark Lentczner wrote:
This does not appear to be the case, at least any more. The way GHC invokes
gcc
for c pre-processing only removes /*…*/ style comments, not the later //
style:
Yes, I can reproduce your behaviour on my system and
An example in the wild is in the package wai-extra, in the
file Network/Wai/Middleware/RequestLogger.hs where the */* construct
appears twice in the comments.
An even more common case could be the operator '//' of the vector package.
cpp also removes C++ style comments.
I once almost got crazy
Hi Ian,
I guess they may not cause any actual problems, but it's certainly nicer
not having them (which is what using submodules gives us).
I don't quite understand how you should get rid of these merge commits
by using submodules, because at the end every submodule is just a git repository
Hi Kazu,
On Thu, Jun 06, 2013 at 10:42:03AM +0900, Kazu Yamamoto wrote:
Please read A successful Git branching model to know why fast-forward
is not used recently.
I think you've to differentiate the case of merging a feature branch
into the master branch and the case of merging a local with
Hi Geoffrey,
I don't know much about subtrees, but that might be another possibility?
the main point about subtrees is, that you've just one repository and
you're merging a directory of this repository with 'git subtree' with
some other git repository.
subtrees and submodules both try to
Hi Nicolas,
On Wed, Jun 05, 2013 at 03:27:09PM +0200, Nicolas Trangez wrote:
As my experience with submodules is positive (though limimted), could
you elaborate on the difficulties/hassle here?
If you would like to develop some kind of feature which involves
changes on multiple
Hi Austin,
On Wed, Jun 05, 2013 at 09:41:56AM -0500, Austin Seipp wrote:
But it's not installed by default with git, it's unclear if it ever will be.
I think subtree has been part of git since 1.7.x .
I have just installed the default git package (git 1.8.1.2) of Ubuntu
13.04 and the subtree
Hi Jan,
On Mon, Mar 25, 2013 at 09:09:26PM +0100, Jan Stolarek wrote:
The problem is that GHC an testsuite are two diferent repositories.
One might commit changes to both of them, but if only one repo is
pushed to the central git server, the problem with failing validation
might occur.
25 matches
Mail list logo
