<div dir="ltr">Was there any consensus on how to move forward on this? I just found another example of <div class="gmail_default" style="font-family:'times new roman',serif;font-size:large;display:inline"></div>8.0 type which is not beginner friendly: <div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>bash-3.2$ ghci </div></div><div><div>GHCi, version 8.0.0.20160204: <a href="http://www.haskell.org/ghc/" target="_blank">http://www.haskell.org/ghc/</a> :? for help</div></div><div><div><div>Prelude> True</div></div></div><div><div><div>True</div></div></div><div><div><div>it :: Bool</div></div></div><div><div>Prelude> True || undefined</div></div><div><div>True</div></div><div><div><b>it :: ?callStack::GHC.Stack.Types.CallStack => Bool</b></div></div></blockquote><div><div><br></div></div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Mar 2, 2016 at 1:56 PM Ericson, John <<a href="mailto:john_ericson@brown.edu" target="_blank">john_ericson@brown.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>I dispute your second point a bit: I consider any Prelude changes a
standard library change than a language change, not withstanding the
fact the Prelude is imported by default. Any beginner-language library
can still be imported from normal code. Likewise a "hygienic copy paste"
would simply import the beginner prelude qualified and mangle
identifiers as necessary.<br><br>I'm inclined to think the Racket way is the only true solution here.<br><br></div></div><div dir="ltr">John</div><div dir="ltr"><br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 24, 2016 at 6:07 PM, Manuel M T Chakravarty <span dir="ltr"><<a href="mailto:chak@justtesting.org" target="_blank">chak@justtesting.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Two notable differences between Racket and the situation in Haskell is that (1) Racket has a full blown IDE to support the staged languages and (2) AFIK any Racket program in a simpler language is still a valid Racket program in a more advanced language. (The latter wouldn’t be the case with, e.g., a Prelude omitting type classes as you need to introduce new names —to avoid overloading— that are no longer valid in the full Prelude.)<br>
<br>
Manuel<br>
<br>
> Eric Seidel <<a href="mailto:eric@seidel.io" target="_blank">eric@seidel.io</a>>:<br>
<div><div>><br>
> On Wed, Feb 17, 2016, at 08:09, Christopher Allen wrote:<br>
>> I have tried a beginner's Prelude with people. I don't have a lot of data<br>
>> because it was clearly a failure early on so I bailed them out into the<br>
>> usual thing. It's just not worth it and it deprives them of the<br>
>> preparedness to go write real Haskell code. That's not something I'm<br>
>> willing to give up just so I can teach _less_.<br>
><br>
> Chris, have you written about your experiences teaching with a<br>
> beginner's Prelude? I'd be quite interested to read about it, as (1) it<br>
> seems like a natural thing to do and (2) the Racket folks seem to have<br>
> had good success with their staged teaching languages.<br>
><br>
> In particular, I'm curious if your experience is in the context of<br>
> teaching people with no experience programming at all, vs programming<br>
> experience but no Haskell (or generally FP) experience. The Racket "How<br>
> to Design Programs" curriculum seems very much geared towards absolute<br>
> beginners, and that could be a relevant distinction.<br>
><br>
> Thanks!<br>
> Eric<br>
> _______________________________________________<br>
> ghc-devs mailing list<br>
> <a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
> <a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
<br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</div></div></blockquote></div><br></div></div></div>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div></div></div>