quot; section, as you
> proposed, but
> "report a bug" wiki page already contains information about that you should
> ask for the account approval:
>
> * https://gitlab.haskell.org/ghc/ghc/-/wikis/report-a-bug
>
> 12.12.2023 12:50, Tom Ellis wrote:
> >
Hello GHC devs,
It is hard for new users to understand how to get their new Gitlab
accounts approved by an administrator. See, for example, these
messages, both in the last ten days:
*
On Thu, Dec 07, 2023 at 12:53:02PM +, Richard Eisenberg wrote:
> I think this is an excellent idea! So excellent, that we've already done it.
> :)
>
> When I try to compile with GHC 9.6.2 (what I have lying around), GHC2021 is
> in effect.
>
> Is there something different you were thinking
FWIW if I try the same command I get all the way through to a normal
exit (which I guess is expected since you're not supposed to be able
to actually obtain a shell via ssh!) so I guess the problem is
specific to you, Simon.
Tom
OpenSSH_8.4p1 Debian-5+deb11u1, OpenSSL 1.1.1n 15 Mar 2022
On Thu, May 18, 2023 at 10:05:34PM +0100, Sam Halliday wrote:
> 1. some programming language communities have a "community build" that
>is periodically built by snapshots of the compiler. This allows
>unexpected regressions to be caught early in the dev cycle and would
>allow the
On Wed, Apr 12, 2023 at 02:32:43PM +0530, Harendra Kumar wrote:
> instance MonadIO m => Monad (T m) where
> return = pure
> (>>=) = undefined
>
> instance MonadTrans T where
> lift = undefined
I guess it's nothing to do with 9.6 per se, but rather the difference
between
*
On Tue, Dec 27, 2022 at 08:33:04PM -0700, Chris Smith wrote:
> This conversation reminds me of a parable I encountered somewhere, in which
> someone declares "I don't understand why this decision was ever made, and I
> we should change it", and someone responds, "No, if you don't understand
> the
On Fri, Jan 28, 2022 at 11:52:00AM -0500, Norman Ramsey wrote:
> > My recommendation: ./hadrian/ghci.
>
> I'm about to change a type definition. This change may wreak havoc in
> many parts of GHC, and this is exactly what I want: I'm looking for
> type-error messages that will tell me what
On Thu, Oct 21, 2021 at 11:10:38AM +0200, Sam Derbyshire wrote:
> I'm also getting error 500 now.
Where? When visiting gitlab.haskell.org in your browser or when
using git on the command line?
Tom
___
ghc-devs mailing list
ghc-devs@haskell.org
On Thu, Oct 21, 2021 at 08:59:48AM +, Simon Peyton Jones via ghc-devs wrote:
> Is it just me, or is Gitlab offline again? I'm getting error code 500.
I just checked the following, which all work fine:
* Navigate to https://gitlab.haskell.org/ghc/haddock (in Firefox)
* git clone
If a sponsor (perhaps the HF) could pay for GitLab to host the service
on our behalf would that be helpful? I don't know whether GHC
development relies deeply on some aspect of our self-hosted setup.
(I suspect it does because otherwise we'd likely be using a free
GitLab tier for open source
On Wed, Jun 02, 2021 at 07:03:25PM +, Richard Eisenberg wrote:
> > To me this seems like a rare opportunity to do something where people
> > will say "Hey look, that formidable Haskell compiler is doing
> > something that's friendlier than the equivalent in any other
> > compiler!". For such
naked error codes we should give URLs whch
directly link to sections in the GHC users guide (or other appropriate
resource).
> Disadvantages:
> The code does not impart semantic meaning. But I argue this is not
> so bad, as even a more descriptive code does not impart a precise
> enough sema
a bit tangential to Richard's original
post).
> On 02-06-21 06:46, Tom Ellis wrote:
> > On Tue, Jun 01, 2021 at 03:40:57PM -0700, Alec Theriault wrote:
> >> Rust has taken an interesting approach for this: every error message is
> >> given a unique number like "E
On Tue, Jun 01, 2021 at 03:40:57PM -0700, Alec Theriault wrote:
> Rust has taken an interesting approach for this: every error message is
> given a unique number like "E0119"
Is there a particularly strong reason to use numbers as codes when we
have the entire space human-readable strings
On Fri, Mar 19, 2021 at 07:08:35PM +, Richard Eisenberg wrote:
> > On Mar 19, 2021, at 2:21 PM, Gershom B wrote:
> > Cc: ad...@haskell.org which remains (since it was set up over five?
> > years ago) the contact address for haskell infra admin stuff.
>
> How would I learn of that address?
On Thu, Mar 11, 2021 at 06:19:46AM -0500, Viktor Dukhovni wrote:
> On Thu, Mar 11, 2021 at 06:05:04AM -0500, Viktor Dukhovni wrote:
> > So the question is why the lookup is failing. To that end compiling a
> > tracing with "strace" the below C program should tell the story:
[...]
> To experiment
A user posted the following to the ghc-proposals repository. Both JB
and RAE suggested ghc-devs as a more appropriate forum. Since I have
no idea whether the user has even ever used a mailing list before I
thought I would lower the activation energy by posting their message
for them.
SPJ Wrote:
> I've just installed WSL2 and built GHC. I get this (single)
> validation failure in libraries/unix/tests/getGroupEntryForName. It
> seems to be just an error message wibble, but I can't push a change
> to master because that'll affect everyone else.
Interesting, I've only ever built
On Wed, Dec 21, 2016 at 01:49:33PM -0600, amin...@gmail.com wrote:
> Additionally, Opaleye uses Arrow syntax pretty heavily iirc.
If I were writing the Opaleye tutorial today (and if I rewrite it) I will
shy away from arrows and encourage users to use applicative style. There's
only one operator
On Wed, Dec 21, 2016 at 05:52:34PM +0100, Boespflug, Mathieu wrote:
> And Opaleye (a successor to haskellDB, for safe interaction with SQL
> databases) also uses arrow notation last I checked. As I recall do-notation
> is too powerful, whereas proc-notation provides exactly the right
> expressive
21 matches
Mail list logo
