<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I just tried Kialo, and couldn't warm to it -- despite being excited to try.<div class=""><br class=""></div><div class="">+ I really like its way of encouraging individual pros and cons, and how these are kept short and independent.</div><div class=""><br class=""></div><div class="">- I can't get *any* forest, only lots and lots of trees. Kialo forces focus on only one thing at a time, but I found myself constantly losing any picture of where I was or where I was going.</div><div class="">- There seems to be no visual indication (to me) of when a node has sub-nodes. For example, if I read a "con" that itself has 5 "cons" underneath, I wouldn't know unless I click on it.</div><div class="">- I think I stumbled into a con of a con of a con. See "I found myself constantly losing any picture of where I was", above.</div><div class="">- There doesn't seem to be a way to agree with an argument, without adding a distinct "pro". This means that if a post is liked by 8 of us and disliked (for different reasons) by 3, there would be 3 cons against it, no pros, and a misrepresentation of our communal opinion.</div><div class=""><br class=""></div><div class="">In its current form, Kialo seems best as a way to organize pros and cons, but to actually have debate elsewhere. If someone out there knows how to mitigate the cons above, I'd be interested.</div><div class=""><br class=""></div><div class="">If Kialo becomes the place where the action is, I'll participate, but I would hope there's a better way. (Not that email threads are necessarily better!)</div><div class=""><br class=""></div><div class="">Richard</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 15, 2020, at 3:27 PM, Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div dir="ltr" class="">On Tue, 15 Dec 2020 at 13:00, Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a>> wrote:<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div lang="EN-GB" style="overflow-wrap: break-word;" class=""><div class="gmail-m_-2081504188946697494WordSection1"><p class="MsoNormal"><span class="">My point is that NamedWildcards is a souped up version of PartialTypeSignatures<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span class="">f :: _ -> _<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class="">g :: _a -> _a<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span class="">The former is a partial type signature. So is the latter! The former is equivalent to f :: _a -> _b.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span class="">Now, I’ve just discovered that<u class=""></u><u class=""></u></span></p><ul type="disc" style="margin-top: 0cm;" class=""><li class="gmail-m_-2081504188946697494MsoListParagraph" style="margin-left: 0cm;"><span class="">Wildcards in types work *<b class="">regardless</b>* of flag. Thus you can use the above signature for f with no flag at all, and get a message like this:<u class=""></u><u class=""></u></span></li></ul><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class="">Foo.hs:5:6: error:<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class=""> <span class="Apple-converted-space"> </span>• Found type wildcard ‘_’ standing for ‘[a]’<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class=""> <span class="Apple-converted-space"> </span>Where: ‘a’ is a rigid type variable bound by<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class=""> <span class="Apple-converted-space"> </span>the inferred type of f :: [a] -> [a]<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class=""> <span class="Apple-converted-space"> </span>at Foo.hs:6:1-12<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494Code" style="margin-left: 72pt;"><span class=""> <span class="Apple-converted-space"> </span>To use the inferred type, enable PartialTypeSignatures<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494MsoListParagraph"><i class=""><span class="">So the only effect of PartialTypeSignatures is to turn that error into a warning.</span></i><span class=""> <span class="Apple-converted-space"> </span>I had not appreciated that.<u class=""></u><u class=""></u></span></p><p class="gmail-m_-2081504188946697494MsoListParagraph"><span class=""><u class=""></u> <u class=""></u></span></p><ul type="disc" style="margin-top: 0cm;" class=""><li class="gmail-m_-2081504188946697494MsoListParagraph" style="margin-left: 0cm;"><span class="">As you say,<span class="Apple-converted-space"> </span></span><span class="">NamedWildCards treats _a as a wildcard rather than a variable. Fine.<u class=""></u><u class=""></u></span></li></ul><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><ul type="disc" style="margin-top: 0cm;" class=""><li class="gmail-m_-2081504188946697494MsoListParagraph" style="margin-left: 0cm;"><span class="">Given the above, I still think it’s bizarre not to allow PartialTypeSignatures. All the complexity is there already; it’s only a question of turning the error into a warning</span></li></ul></div></div></blockquote><div class=""><br class=""></div><div class="">It would be slightly strange to have a language feature that is enabled by default but generates a warning every time you use it. I'd rather the warning was disabled by default, but I agree that PartialTypeSignatures should be on.</div><div class=""><br class=""></div><div class="">If I recall correctly, it was Richard who argued for NamedWildCards without PartialTypeSignatures (or independently of it), somewhere deep in one of these email threads :)<br class=""></div><div class=""><br class=""></div><div class="">Cheers</div><div class="">Simon</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div lang="EN-GB" style="overflow-wrap: break-word;" class=""><div class="gmail-m_-2081504188946697494WordSection1"><ul type="disc" style="margin-top: 0cm;" class=""><li class="gmail-m_-2081504188946697494MsoListParagraph" style="margin-left: 0cm;"><span class=""><u class=""></u><u class=""></u></span></li></ul><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span class="">Simon<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><div style="border-color: currentcolor currentcolor currentcolor blue; border-style: none none none solid; border-width: medium medium medium 1.5pt; padding: 0cm 0cm 0cm 4pt;" class=""><div class=""><div style="border-color: rgb(225, 225, 225) currentcolor currentcolor; border-style: solid none none; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;" class=""><p class="MsoNormal"><b class=""><span lang="EN-US" class="">From:</span></b><span lang="EN-US" class=""><span class="Apple-converted-space"> </span>Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" target="_blank" class="">trupill@gmail.com</a>><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>15 December 2020 12:48<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com" target="_blank" class="">simonpj@microsoft.com</a>><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank" class="">mail@joachim-breitner.de</a>>;<span class="Apple-converted-space"> </span><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [ghc-steering-committee] #380 GHC2021: Forth status update /<span class="Apple-converted-space"> </span><a href="http://kialo.com/" target="_blank" class="">kialo.com</a><u class=""></u><u class=""></u></span></p></div></div><p class="MsoNormal"><u class=""></u> <u class=""></u></p><div class=""><p class="MsoNormal" style="margin-bottom: 12pt;"><u class=""></u> <u class=""></u></p><div class=""><div class=""><p class="MsoNormal">On 15 Dec 2020 at 13:18:20, Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a>> wrote:<u class=""></u><u class=""></u></p></div><blockquote style="border-color: currentcolor currentcolor currentcolor rgb(204, 204, 204); border-style: none none none solid; border-width: medium medium medium 1pt; padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;" class=""><div class=""><p class="MsoNormal">Writing down the summary here<br class=""><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1BMJtUQGk1HKOFgLnczybAwd1HgqbNpZA7elM4VnANa8%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977856035%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nwXI1KIFwaFAf8WrdnXBF7MoNIhq2tTt0KIL0LVBCx8%3D&reserved=0" target="_blank" class="">https://docs.google.com/document/d/1BMJtUQGk1HKOFgLnczybAwd1HgqbNpZA7elM4VnANa8/edit?usp=sharing</a><br class=""><br class="">allows me to ask:<br class=""><br class="">* It can't be sensible to propose NamedWildCards (8 votes) without ParitalTypeSignatures (2 votes), can it?<u class=""></u><u class=""></u></p></div></blockquote><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">As far as I understand it, they have different purposes:<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">- NamedWildCards instructs GHC to treat names starting with underscore as unknown variables when unifying. So for example, the following would not work, since _a would need to be Char and Bool at the same time.<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">> f :: _a -> _a<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal">> f ‘x’ = True<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">If you do not enable NamedWildCards, names starting with an underscore are taken to be regular variables. So the type ‘_a -> _a’ is completely equivalent to ‘a -> a’.<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">- PartialTypeSignatures is about *accepting* those signatures by the compiler. If you don’t have this on, a partial type signature gives you an error with the inferred type, but does not continue compiling your program.<u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><p class="MsoNormal">Personally, I think this is the right behaviour: do not accept partial signatures unless explicitly told so.<u class=""></u><u class=""></u></p></div><p class="MsoNormal"><u class=""></u> <u class=""></u></p><blockquote style="border-color: currentcolor currentcolor currentcolor rgb(204, 204, 204); border-style: none none none solid; border-width: medium medium medium 1pt; padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;" class=""><div class=""><p class="MsoNormal"><br class="">Simon<br class=""><br class="">| -----Original Message-----<br class="">| From: ghc-steering-committee <ghc-steering-committee-<br class="">| <a href="mailto:bounces@haskell.org" target="_blank" class="">bounces@haskell.org</a>> On Behalf Of Joachim Breitner<br class="">| Sent: 14 December 2020 22:23<br class="">| To:<span class="Apple-converted-space"> </span><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class="">| Subject: [ghc-steering-committee] #380 GHC2021: Forth status update /<br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkialo.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977866031%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EHZIchQsOdwrT6p5MuQUoWONZvUr8x35ACzUXFZk1HA%3D&reserved=0" target="_blank" class="">kialo.com</a><br class="">| <br class="">| Dear Committe,<br class="">| <br class="">| three weeks in, we have all votes. So now things are looking more<br class="">| concrete.<br class="">| <br class="">| As always, the table<br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith" target="_blank" class="">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith</a><br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fub.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977866031%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zmCppIBCXjqoVaZaXY1FWcKBcBBP8Pwni1jn7hkpBcU%3D&reserved=0" target="_blank" class="">ub.com</a>%2Fghc-proposals%2Fghc-<br class="">| proposals%2Fblob%2Fghc2021%2Fproposals%2F0000-<br class="">| ghc2021.rst%23data&data=04%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977876027%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yWWXXXYhlgsc6DkoQ2pl%2Fg3W3FKR6wrlSN70mYDCoWE%3D&reserved=0" target="_blank" class="">40microsoft.com</a>%7C10d0e7<br class="">| 09a1dd4525973708d8a07ecdad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%<br class="">| 7C637435813779684920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI<br class="">| joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3i5Pfxw2%2B<br class="">| XKtfsbkhbwjreFArYCfvMDGyw%2F0ctxJfKs%3D&reserved=0<br class="">| has the current data.<br class="">| <br class="">| Would it be helpful to add columns to that table for each committee<br class="">| member? So that you can quickly see who voted what?<br class="">| <br class="">| The following in are safely in (= need more than one vote to change to<br class="">| get out):<br class="">| <br class="">| BangPatterns, BinaryLiterals, ConstrainedClassMethods,<br class="">| ConstraintKinds, DeriveDataTypeable, DeriveFoldable, DeriveFunctor,<br class="">| DeriveGeneric, DeriveLift, DeriveTraversable, EmptyCase,<br class="">| EmptyDataDecls, EmptyDataDeriving, ExplicitForAll, FlexibleContexts,<br class="">| FlexibleInstances, GADTSyntax, GeneralisedNewtypeDeriving,<br class="">| HexFloatLiterals, ImportQualifiedPost, InstanceSigs, KindSignatures,<br class="">| MultiParamTypeClasses, NamedFieldPuns, NumericUnderscores, PolyKinds,<br class="">| PostfixOperators, RankNTypes, StandaloneDeriving, StarIsType,<br class="">| TypeApplications, TypeSynonymInstances<br class="">| <br class="">| The following are barely in (exactly 8 votes in favor, and 3 against):<br class="">| <br class="">| ExistentialQuantification, NamedWildCards, StandaloneKindSignatures,<br class="">| TypeOperators<br class="">| <br class="">| The following are short one vote (7 in favor, 4 against):<br class="">| <br class="">| DerivingStrategies, ForeignFunctionInterface, GADTs, MonoLocalBinds,<br class="">| NegativeLiterals, RecordWildCards, ScopedTypeVariables, TupleSections,<br class="">| TypeFamilies<br class="">| <br class="">| <br class="">| I am sure we can have plenty of discussion for each of these. Probably<br class="">| without end. As Simon says, mailing lists don't scale. So I think we<br class="">| have two choices:<br class="">| <br class="">| 1. Let the numbers decide, and accept whatever comes out. According to<br class="">| the process (which we should only follow if we find it helpful) we'd<br class="">| maybe update our votes, and maybe point out new facets, for one week,<br class="">| and then just take whatever has 8 votes.<br class="">| <br class="">| or<br class="">| <br class="">| 2. Explore a more efficient discussion format.<br class="">| <br class="">| For the latter I mentioned<span class="Apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkialo.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977886022%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Qq0Ly%2Bi0BEtojVpMvmN9GqDs0ftVQp9%2B5DA0RQel7JI%3D&reserved=0" target="_blank" class="">kialo.com</a><span class="Apple-converted-space"> </span>before, and maybe it is worth a<br class="">| try, so I set up a discussion there:<br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww" target="_blank" class="">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww</a>.<br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkialo.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977886022%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Qq0Ly%2Bi0BEtojVpMvmN9GqDs0ftVQp9%2B5DA0RQel7JI%3D&reserved=0" target="_blank" class="">kialo.com</a>%2Fwhich-haskell-extensions-should-go-into-ghc2021-<br class="">| 43548%3Fpath%3D43548.0&data=04%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977896016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gNhldU3ky0zZjdTamtkGkcXkYnij%2FnZfXZP%2FVA7pBh4%3D&reserved=0" target="_blank" class="">40microsoft.com</a>%7C10<br class="">| d0e709a1dd4525973708d8a07ecdad%7C72f988bf86f141af91ab2d7cd011db47%7C1%<br class="">| 7C0%7C637435813779684920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL<br class="">| CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=I8nLXqK<br class="">| Mf32ctvlrPcPS%2BKBD%2FSw5vrV%2B0Fv%2BYvP%2Bbho%3D&reserved=0<br class="">| <br class="">| So what do you see there?<br class="">| <br class="">| There is a discussion tree:<br class="">| <br class="">| The root is "what goes in GHC2021"<br class="">| <br class="">| The next layer are all extensions with 7 or 8 votes.<br class="">| (I assume we should focus on those initially, but feel free to add<br class="">| more or ask me to.) For example: TupleSections<br class="">| <br class="">| And then each of these has a column where we can collect Pros and<br class="">| cons.<br class="">| For example:<br class="">| Pro: Opt-in Syntax<br class="">| Con: Possible clash with extra-comma syntax extensions.<br class="">| <br class="">| So you can treat it like a wiki, but with structure to organize the<br class="">| discussion.<br class="">| <br class="">| In fact, each pro and con is itself a node where you can add<br class="">| supporting and disagreeing comments. This means that if you _disagree_<br class="">| that TupleSections are actually Opt-in syntax, there is a dedicated<br class="">| place to raise that point, rather than putting "Not actually opt-in"<br class="">| in the Con column of TupleSections...<br class="">| <br class="">| A good way to navigate the discussion seems to be the radial icon in<br class="">| the top left; it opens a radial view of the whole discussion, and you<br class="">| can read arguments by hovering.<br class="">| <br class="">| <br class="">| The site doesn't offer voting, it is only about structuring the<br class="">| discussion, and it is designed for much larger and much more<br class="">| contentious debates (e.g. "Brexit"). So we'll see how well it works<br class="">| for us and if it's helpful.<br class="">| <br class="">| Cheers,<br class="">| Joachim<br class="">| <br class="">| <br class="">| --<br class="">| Joachim Breitner<br class="">| <a href="mailto:mail@joachim-breitner.de" target="_blank" class="">mail@joachim-breitner.de</a><br class="">| <br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.j" target="_blank" class="">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.j</a><br class="">| oachim-<br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbreitner.de%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977896016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gDY7g2ZbZUXmBOcZ965QbDXx%2FyqV0QTzLy28JY6PnTI%3D&reserved=0" target="_blank" class="">breitner.de</a>%2F&data=04%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977906015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=um%2Ba0XdBybuyBixCbfruJUGQRyHy%2BBaXDGbgFWIAu2k%3D&reserved=0" target="_blank" class="">40microsoft.com</a>%7C10d0e709a1<br class="">| dd4525973708d8a07ecdad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63<br class="">| 7435813779684920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV<br class="">| 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7N%2FDBw%2BRwVr<br class="">| DcVqSS7BQroJAg8R3ccoLQ9Hua%2FgwbAE%3D&reserved=0<br class="">| <br class="">| <br class="">| _______________________________________________<br class="">| ghc-steering-committee mailing list<br class="">| <a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class="">| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail" target="_blank" class="">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a><br class="">| .<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhaskell.org%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977916012%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iiZXGZCSRr4RgU0zb3UtblBFxJYUeM%2B8JBZ6goNbQsY%3D&reserved=0" target="_blank" class="">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br class="">| committee&data=04%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977916012%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=o9BSWTudDLBqHILOY4c52gYrO7col9hS5OcJ6JTDT1k%3D&reserved=0" target="_blank" class="">40microsoft.com</a>%7C10d0e709a1dd452<br class="">| 5973708d8a07ecdad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374358<br class="">| 13779684920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz<br class="">| IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=byGDRSmjPqFiUAGe5fjF<br class="">| vrhFIuQCjAldYzwMCrzrIac%3D&reserved=0<br class="">_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=04%7C01%7Csimonpj%40microsoft.com%7C2aecc7661e8b44021c5508d8a0f7b034%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637436332977926004%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iS6WeND3u5ArOZHO2KRvfEe1gV9%2BySwH%2BaeJbZQtMhg%3D&reserved=0" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><u class=""></u><u class=""></u></p></div></blockquote></div></div></div></div></div>_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class=""></blockquote></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">ghc-steering-committee mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:ghc-steering-committee@haskell.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">ghc-steering-committee@haskell.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a></div></blockquote></div><br class=""></div></body></html>