Please review #387: The Char kind, Shepherd: Alejandro
Dear Committee, this is your secretary speaking: The Char Kind has been proposed by Daniel Rogozin https://github.com/ghc-proposals/ghc-proposals/pull/387 https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-ki... I’ll propose Alejandro as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
Dear Committee, This proposal adds a kind-level ‘Char’ in a similar way as other built-in types, and an API to work with them and with Symbols. My recommendation is to accept the proposal: it fills a gap in our current kind-level machinery in the most minimal way. Regards, Alejandro On 7 Jan 2021 at 12:33:33, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
The Char Kind has been proposed by Daniel Rogozin https://github.com/ghc-proposals/ghc-proposals/pull/387
https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-ki...
I’ll propose Alejandro as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
I have no real opinion either way. The meat of the proposal is in the choice of type families. Are they reasonable? Probably. So I'm probably in favour, though I could easily be swayed either way. On Thu, Jan 7, 2021 at 5:38 PM Alejandro Serrano Mena <trupill@gmail.com> wrote:
Dear Committee, This proposal adds a kind-level ‘Char’ in a similar way as other built-in types, and an API to work with them and with Symbols. My recommendation is to accept the proposal: it fills a gap in our current kind-level machinery in the most minimal way.
Regards, Alejandro
On 7 Jan 2021 at 12:33:33, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
The Char Kind has been proposed by Daniel Rogozin https://github.com/ghc-proposals/ghc-proposals/pull/387
https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-ki...
I’ll propose Alejandro as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
I'm in favor of this proposal, for the reasons Alejandro gives: it fills a gap, and it's about as minimal as we can have. Thanks, Richard
On Jan 7, 2021, at 12:02 PM, Spiwack, Arnaud <arnaud.spiwack@tweag.io> wrote:
I have no real opinion either way. The meat of the proposal is in the choice of type families. Are they reasonable? Probably. So I'm probably in favour, though I could easily be swayed either way.
On Thu, Jan 7, 2021 at 5:38 PM Alejandro Serrano Mena <trupill@gmail.com <mailto:trupill@gmail.com>> wrote: Dear Committee, This proposal adds a kind-level ‘Char’ in a similar way as other built-in types, and an API to work with them and with Symbols. My recommendation is to accept the proposal: it fills a gap in our current kind-level machinery in the most minimal way.
Regards, Alejandro
On 7 Jan 2021 at 12:33:33, Joachim Breitner <mail@joachim-breitner.de <mailto:mail@joachim-breitner.de>> wrote: Dear Committee,
this is your secretary speaking:
The Char Kind has been proposed by Daniel Rogozin https://github.com/ghc-proposals/ghc-proposals/pull/387 <https://github.com/ghc-proposals/ghc-proposals/pull/387> https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-ki... <https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-kind.rst>
I’ll propose Alejandro as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process <https://github.com/ghc-proposals/ghc-proposals#committee-process>
Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de <mailto:mail@joachim-breitner.de> http://www.joachim-breitner.de/ <http://www.joachim-breitner.de/>
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org <mailto:ghc-steering-committee@haskell.org> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee <https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee> _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org <mailto:ghc-steering-committee@haskell.org> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee <https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee> _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
There are no more concerns left in the GitHub thread, and nobody has raised any concerns. I think this proposal is ready for merge. Alejandro El El jue, 7 ene 2021 a las 18:05, Richard Eisenberg <rae@richarde.dev> escribió:
I'm in favor of this proposal, for the reasons Alejandro gives: it fills a gap, and it's about as minimal as we can have.
Thanks, Richard
On Jan 7, 2021, at 12:02 PM, Spiwack, Arnaud <arnaud.spiwack@tweag.io> wrote:
I have no real opinion either way. The meat of the proposal is in the choice of type families. Are they reasonable? Probably. So I'm probably in favour, though I could easily be swayed either way.
On Thu, Jan 7, 2021 at 5:38 PM Alejandro Serrano Mena <trupill@gmail.com> wrote:
Dear Committee, This proposal adds a kind-level ‘Char’ in a similar way as other built-in types, and an API to work with them and with Symbols. My recommendation is to accept the proposal: it fills a gap in our current kind-level machinery in the most minimal way.
Regards, Alejandro
On 7 Jan 2021 at 12:33:33, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
The Char Kind has been proposed by Daniel Rogozin https://github.com/ghc-proposals/ghc-proposals/pull/387
https://github.com/serokell/ghc-proposals/blob/master/proposals/0000-char-ki...
I’ll propose Alejandro as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
Am Freitag, den 22.01.2021, 12:18 +0100 schrieb Alejandro Serrano Mena:
There are no more concerns left in the GitHub thread, and nobody has raised any concerns. I think this proposal is ready for merge.
Merged -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
participants (4)
-
Alejandro Serrano Mena -
Joachim Breitner -
Richard Eisenberg -
Spiwack, Arnaud