Re: GHC's Fall 2018 HCAR submission

Artem Pelenitsyn writes: > Ben, > > I assume, writing a Pandoc writer for TracWiki shouldn't be that hard. > Would that be of any help? > Well, there would need to be both a reader and a writer, since we ultimately need to end up with TeX. Indeed having these would help immensely. Cheers, -

The future of Phabricator

TL;DR. For several reasons I think we should consider alternatives to Phabricator. My view is that GitLab seems like the best option. Hello everyone, Over the past year I have been growing increasingly weary of our continued dependence on Phabricator. Without a doubt, its code review

Re: GHC's Fall 2018 HCAR submission

Ben, I assume, writing a Pandoc writer for TracWiki shouldn't be that hard. Would that be of any help? -- Best, Artem On Mon, 29 Oct 2018 at 16:39 Ben Gamari wrote: > Artem Pelenitsyn writes: > > > Hi Ben, > > > > I see. Have you considered using online converting tools like > >

Re: GHC's Fall 2018 HCAR submission

Artem Pelenitsyn writes: > Hi Ben, > > I see. Have you considered using online converting tools like > try-pandoc[1]? Is it still painful? > I do use Pandoc to convert from Markdown to Latex. However, Pandoc does not support Trac's wiki syntax. Cheers, - Ben signature.asc Description: PGP

Re: GHC's Fall 2018 HCAR submission

Hi Ben, I see. Have you considered using online converting tools like try-pandoc[1]? Is it still painful? [1]: https://pandoc.org/try/ On Mon, 29 Oct 2018 at 15:32 Ben Gamari wrote: > Artem Pelenitsyn writes: > > > On Mon, 29 Oct 2018 at 14:25 Evan Laforge wrote: > > > >> Also, when I copy

Re: Using GHC Core as a Language Target

That’s a brilliant resource! Thanks so much for the links. _ara > On 29 Oct 2018, at 19:11, Csaba Hruska wrote: > > There is also a nice intro blog post about GHC internals with an example how > to compile a custom constructed module AST. > Dive into GHC: Pipeline > Dive into GHC:

Re: GHC's Fall 2018 HCAR submission

Artem Pelenitsyn writes: > On Mon, 29 Oct 2018 at 14:25 Evan Laforge wrote: > >> Also, when I copy paste the links in the "At the time of writing" >> section, the backslashes in the search query mess it up. Maybe a >> markdown rendering step would remove those? >> > > I'm not sure It makes

Re: Using GHC Core as a Language Target

There is also a nice intro blog post about GHC internals with an example how to compile a custom constructed module AST. - Dive into GHC: Pipeline - Dive into GHC: Intermediate Forms - Dive

Re: GHC's Fall 2018 HCAR submission

On Mon, 29 Oct 2018 at 14:25 Evan Laforge wrote: > Also, when I copy paste the links in the "At the time of writing" > section, the backslashes in the search query mess it up. Maybe a > markdown rendering step would remove those? > I'm not sure It makes much sense to use {{{...}}} to format

Re: GHC's Fall 2018 HCAR submission

There are some incomplete sentences under "Further improvements to runtime performance:" Also, congratulations to Tamar Christina for becoming the new IO manager! Also, when I copy paste the links in the "At the time of writing" section, the backslashes in the search query mess it up. Maybe a

CI status

Hi everyone, As you likely have noticed, GHC's CI is a bit of a mess since the Hadrian merge, especially for differentials based on commits prior to the merge. The problem is a tiresome limitation of Harbormaster's CI strategy [1]. I have taken this opportunity to finally move testing of

Re: Suppressing False Incomplete Pattern Matching Warnings for Polymorphic Pattern Synonyms

I've just found this related ticket: https://ghc.haskell.org/trac/ghc/ticket/14422 On 10/26/18 7:04 PM, Richard Eisenberg wrote: Aha. So you're viewing complete sets as a type-directed property, where we can take a type and look up what complete sets of patterns of that type might be.