<div dir="ltr">I like the flag idea mentioned by Eric Seidel:<div><br></div><div>> <span style="color: rgb(0, 0, 0); white-space: pre-wrap;">Perhaps instead of changing the default behavior of :type or adding new</span><pre style="white-space: pre-wrap; color: rgb(0, 0, 0);">commands, we could add a flag to enhance :type's output.</pre><pre style="white-space: pre-wrap; color: rgb(0, 0, 0);"><br></pre><pre style="white-space: pre-wrap; color: rgb(0, 0, 0);">Would it be overkill to have two flags, one that enabled showing the full type + specializations, and a "newbie mode" flag that only showed a few specializations?</pre><pre style="white-space: pre-wrap; color: rgb(0, 0, 0);"><br></pre><pre style="white-space: pre-wrap; color: rgb(0, 0, 0);">Daniel.</pre><br>On Wednesday, April 27, 2016 at 2:34:29 PM UTC+2, Takenobu Tani wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir="ltr"><div>Dear cafe,</div><div><br></div><div>I'm forwarding mail from ghc-devs ML [1].</div><div><br></div><div>I think `:type` command is very important for beginners and middle users.</div><div>Please feedback your opinion to them ;)</div><div><br></div><div>[1]: <a href="https://mail.haskell.org/pipermail/ghc-devs/2016-April/011933.html" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fmail.haskell.org%2Fpipermail%2Fghc-devs%2F2016-April%2F011933.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEx-rcK99vRyt2xtjWYdSEs7nN_bg';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fmail.haskell.org%2Fpipermail%2Fghc-devs%2F2016-April%2F011933.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEx-rcK99vRyt2xtjWYdSEs7nN_bg';return true;">https://mail.haskell.org/<wbr>pipermail/ghc-devs/2016-April/<wbr>011933.html</a></div><div><br></div><div><br></div><div>> 2016-04-26 22:08 GMT+09:00 Richard Eisenberg <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="_niTb3AYBgAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">e...@cis.upenn.edu</a>>:</div><div>> Hi devs,</div><div>> </div><div>> Over the weekend, I was pondering the Haskell course I will be teaching next year and shuddered at having to teach Foldable at the same time as `length`. So I implemented feature request #10963 (<a href="https://ghc.haskell.org/trac/ghc/ticket/10963" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fghc.haskell.org%2Ftrac%2Fghc%2Fticket%2F10963\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHjASBlCalf1NpGfDnrYHpx0O4SMg';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fghc.haskell.org%2Ftrac%2Fghc%2Fticket%2F10963\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHjASBlCalf1NpGfDnrYHpx0O4SMg';return true;">https://ghc.haskell.org/trac/<wbr>ghc/ticket/10963</a>), which allows for a way for a user to request a specialization of a type. It all works wonderfully, but there is a real user-facing design issue here around the default behavior of :type and whether or not to add new :type-y like commands. I have outlined the situation here: <a href="https://ghc.haskell.org/trac/ghc/wiki/Design/GHCi/Type" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fghc.haskell.org%2Ftrac%2Fghc%2Fwiki%2FDesign%2FGHCi%2FType\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGjplmDBOzq8tn8S0iQ8EF-YtuomQ';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fghc.haskell.org%2Ftrac%2Fghc%2Fwiki%2FDesign%2FGHCi%2FType\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGjplmDBOzq8tn8S0iQ8EF-YtuomQ';return true;">https://ghc.haskell.org/trac/<wbr>ghc/wiki/Design/GHCi/Type</a></div><div>> </div><div>> I'd love some broad input on this issue. If you've got a stake in how this all works, please skim that wiki page and comment on #10963.</div><div>> </div><div>> Thanks!</div><div>> Richard</div><div><br></div><div>Cheers,</div><div>Takenobu</div><div><br></div></div>
</blockquote></div></div>