Personal tools

Talk:Typeclassopedia

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(References/bibliography: new section)
(<code> vs <hask> tags: new section)
Line 21: Line 21:
   
 
I'm not entirely happy about the situation with citations. Although I like having inline links, a bunch of information is lost by just giving a link rather than a full bibliography entry. I plan to add more citations so just linking to the old .bib file is insufficient. What would be the best way to maintain the actual citation/bibliography info? Is it as easy as copying over some wikipedia citation templates? --[[User:Byorgey|Byorgey]] 18:46, 26 November 2011 (UTC)
 
I'm not entirely happy about the situation with citations. Although I like having inline links, a bunch of information is lost by just giving a link rather than a full bibliography entry. I plan to add more citations so just linking to the old .bib file is insufficient. What would be the best way to maintain the actual citation/bibliography info? Is it as easy as copying over some wikipedia citation templates? --[[User:Byorgey|Byorgey]] 18:46, 26 November 2011 (UTC)
  +
  +
== &lt;code&gt; vs &lt;hask&gt; tags ==
  +
  +
I'd like to standardize on using &lt;haskell&gt; tags to surround code blocks, but &lt;code&gt; tags to surround inline code. My reasons:
  +
# &lt;hask&gt; tags seem to break a lot of things (e.g. they cannot be used inside links, etc.)
  +
# The formatting with &lt;hask&gt; tags is inconsistent: <hask>Monad</hask> and <hask>Applicative</hask> are different colors, <hask>&&&</hask> does not look right, etc. Even if the formatting were ''consistent'' it would still be ''distracting'': having different sorts of things be different colors helps when reading a code block, because it gives you some visual structure. Having different-colored things in the middle of paragraphs, on the other hand, only serves to distract one's attention when trying to read.

Revision as of 01:53, 27 November 2011

Contents

1 Adding Exercises

I'd like to add a bunch of explicit, typographically distinguished exercises to the text. For example, the Haskell wikibook typesets exercises in a centered box. I don't know a lot about wiki markup -- does anyone have ideas on a good way to do this?

Byorgey 16:09, 26 November 2011 (UTC)


https://en.wikibooks.org/wiki/Template:Exercises If you look at the source, it doesn't seem too complicated to copy over - only calls 1 or 2 other templates an those may not be important. --Gwern 16:20, 26 November 2011 (UTC)

That works great, thanks! Byorgey 17:34, 26 November 2011 (UTC)

2 §6.4 Other monoidal classes

This section states that instances of Alternative/MonadPlus/ArrowPlus are sometimes the same as the Monoid instance, and sometimes different. It would be helpful (imo) if it was explained why this is: whether it would be better if instances of Alternative/MonadPlus/ArrowPlus were the same as the Monoid instance, and that sometimes they are not due to accidents of history; or whether sometimes these instances should be different, and giving guidance as to when those times are.

--Dave4420 17:16, 26 November 2011 (UTC)

Hmm, where does it say that? Byorgey 17:40, 26 November 2011 (UTC)

3 References/bibliography

I'm not entirely happy about the situation with citations. Although I like having inline links, a bunch of information is lost by just giving a link rather than a full bibliography entry. I plan to add more citations so just linking to the old .bib file is insufficient. What would be the best way to maintain the actual citation/bibliography info? Is it as easy as copying over some wikipedia citation templates? --Byorgey 18:46, 26 November 2011 (UTC)

4 <code> vs <hask> tags

I'd like to standardize on using <haskell> tags to surround code blocks, but <code> tags to surround inline code. My reasons:

  1. <hask> tags seem to break a lot of things (e.g. they cannot be used inside links, etc.)
  2. The formatting with <hask> tags is inconsistent:
    Monad
    and
    Applicative
    are different colors,
    &&&
    does not look right, etc. Even if the formatting were consistent it would still be distracting: having different sorts of things be different colors helps when reading a code block, because it gives you some visual structure. Having different-colored things in the middle of paragraphs, on the other hand, only serves to distract one's attention when trying to read.