Is there a reason you want to stick with 8.6.5?
One way to find what you want is to use git-bisect to find the commit that made
the change. I think various people have automated setups for this.
Simon
From: ghc-devs On Behalf Of Chris Smith
Sent: 14 June 2020 14:43
To: ghc-devs@haskell.org
Su
In light of the mentioned patch, I prefer to freeze my activity about the
unification of Nat and Natural up to the merging this patch. After that, I
am going to rebase my branch and make MR. Thank you, Ben!
пн, 15 июн. 2020 г. в 00:32, Ben Gamari :
> Rinat Stryungis writes:
>
> > Hi. I have a qu
I’ve always thought that whole-program compilation has the possibility of doing
optimisations that are simply inaccessible without the whole program, but been
daunted by the engineering challenges of making WPC actually work. So it’s
fantastic that you’ve made progress on this. Well done!
Que
Does anyone know how to search better in GitLab.
Currently I'm using the standard GitLab search. I'm searching for
"<>"
where I intend the quotes meaning exactly that string as usual in a search
term. But I get lots of results mentioning loop, without the angle brackets.
Moreover I want to sort
> Does Google index our repo? Can I use Google to search it somehow?
In google you can type:
site:gitlab.haskell.org "<>"
Cheers,
Sylvain
On 15/06/2020 11:48, Simon Peyton Jones via ghc-devs wrote:
Does anyone know how to search better in GitLab.
Currently I’m using the standard GitLab s
I've used the site:gitlab.haskell.org trick on Google for some time. Recently
(last month or so?) I've found that it's much less useful. I can't quantify
this, other than the fact that I find myself frequently displeased with the
result. It does seem that Google indexes our site less frequently
My reason for sticking with 8.6.5 is that I don't yet trust GHCJS with
later GHC versions. Thanks everyone for the pointers and suggestions.
I'll look further into this when I have more time. (Alas, it's not my
full-time job, so that's probably not until the weekend.)
On Mon, Jun 15, 2020 at 5:1
Simon Peyton Jones via ghc-devs writes:
> Does anyone know how to search better in GitLab.
> Currently I'm using the standard GitLab search. I'm searching for
> "<>"
> where I intend the quotes meaning exactly that string as usual in a search
> term. But I get lots of results mentioning loop,
> On Jun 15, 2020, at 6:50 PM, Ben Gamari wrote:
>
> Richard, I checked on Google Search Console and it appears to be
> indexed on a nearly-daily basis. I'm a bit surprised that you have been
> having trouble. Do you have a specific example of a query that you have
> been disappointed by in the
On 15/06/2020 19:50, Ben Gamari wrote:
Frankly, this makes me wonder whether we should change the output
produced for loops. The current error is essentially un-Googleable, as
we see here. I know I have personally struggled with this same issue in
the past.
I wholeheartedly agree with this sugg
| Frankly, this makes me wonder whether we should change the output
| produced for loops. The current error is essentially un-Googleable, as
| we see here. I know I have personally struggled with this same issue in
| the past.
I'd be fine with that. <> is pretty cryptic.
Simon
| -Origi
As a side note, the idea of making a taxonomy of errors with unique tagging
has been brought up on ghc-proposals recently, although marked as
out-of-scope (maybe rightly so):
https://github.com/ghc-proposals/ghc-proposals/pull/325
The ease of searching is among the major motivations behind it.
--
Thank you for referencing the issue, I couldn't find it anymore for some
reason.
While the technicality of the "errors-as-values" proposal might delay
the implementation of such a taxonomy,
I think we could totally lay the groundwork and actually work on
defining it first.
On 15/06/2020 23:2
13 matches
Mail list logo
