[ghc-steering-committee] [ghc-proposals/ghc-proposals] Support ergonomic dependent types (#378)

Simon Peyton Jones simonpj at microsoft.com
Tue Mar 9 15:36:21 UTC 2021


(Writing to the committee rather than polluting the DT proposal thread.)

We have a bullet "Does not create a language fork" in the review criteria<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%23review-criteria&data=04%7C01%7Csimonpj%40microsoft.com%7C2d39084e129047d031f508d8e3044dca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637508954935323802%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=F0fX%2BB%2BjH7xfJWoiYxNOfJRFvo6vix6HhwID5%2FXt1EU%3D&reserved=0>. I treat it like the other criteria, a fork-like proposal is a red flag, but not an automatic reject.
This relates back to our earlier conversation about proposal properties.  Eric suggested:


  *   Backward compatibility.  Does an extension *expand* the language or *change* it? In other words, does an extension strictly accept more programs than before, or can it change the meaning of existing programs, or even reject previously valid programs?


  *   Plausible default.   Do we expect the extension to eventually be on-by-default (in GHCxxxx) and effectively disappear, or will it continue to be opt-in?   -XStrict or -XRebindableSyntax are examples of an extension that we want, but that are not plausible defaults.


  *   Localised.  Is an extension *contained* within a module or is it *infectious*? Does my choice of extensions when writing a module affect which extensions downstream clients must enable? (I would say most extensions are contained, e.g. you can apply a type family without enabling TypeFamilies or match on a pattern synonym without enabling PatternSynonyms. However, you cannot call a function that takes an implicit parameter without enabling ImplicitParams.)

Reading our "fork-like" criterion, it seems to be saying "it's fork-like if it is not a plausible default (in the above sense), and fork-like is bad".  But as -XStrict and -XRebindableSyntax show, not being a plausible default isn't necessarily bad.

Do we want to revise our language in the criteria?

Simon



From: Eric Seidel <notifications at github.com>
Sent: 09 March 2021 14:05
To: ghc-proposals/ghc-proposals <ghc-proposals at noreply.github.com>
Cc: Simon Peyton Jones <simonpj at microsoft.com>; Assign <assign at noreply.github.com>
Subject: Re: [ghc-proposals/ghc-proposals] Support ergonomic dependent types (#378)


Do we have a write up of what it means to be fork-like? Or what role the fork-like property plays in our deliberations?

We have a bullet "Does not create a language fork" in the review criteria<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%23review-criteria&data=04%7C01%7Csimonpj%40microsoft.com%7C2d39084e129047d031f508d8e3044dca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637508954935323802%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=F0fX%2BB%2BjH7xfJWoiYxNOfJRFvo6vix6HhwID5%2FXt1EU%3D&reserved=0>. I treat it like the other criteria, a fork-like proposal is a red flag, but not an automatic reject.

-
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F378%23issuecomment-793940902&data=04%7C01%7Csimonpj%40microsoft.com%7C2d39084e129047d031f508d8e3044dca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637508954935333797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=GEe4ZWVbIpjkzC%2BSt7lP3NHIeeUgXY6eQEys8wFt1U8%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAEOY6Y6WR6HKU6KFAV2YS3TCYMHDANCNFSM4TVJPUXQ&data=04%7C01%7Csimonpj%40microsoft.com%7C2d39084e129047d031f508d8e3044dca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637508954935333797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=r82A2uAz7kdd85xUqy0N%2FBPJB1sYhBuOTDcbFQ6c4fY%3D&reserved=0>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20210309/1f5b7fd4/attachment.html>


More information about the ghc-steering-committee mailing list