StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16965292
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-06T14:50:52.753
FavoriteCount
0
LastActivityDate
2013-06-06T14:50:52.753
LastEditDate
LastEditorUserId
0
OwnerUserId
1463507
ParentId
16964732
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
This is an excellent use case for <a href="http://www.haskell.org/haskellwiki/Applicative_functor#Usage" rel="noreferrer" title="HaskellWiki/Applicative Functors">applicative style</a>. You can replace your entire snippet (after importing <code>Control.Applicative</code>) with <pre><code>Node <$> numberNode x <*> numberTree t1 <*> numberTree t2 </code></pre> Think of the applicative style (using <code><$></code> and <code><*></code>) as "lifting" function application so it works on functors as well. If you mentally ignore <code><$></code> and <code><*></code> it looks quite a lot like normal function application! Applicative style is useful whenever you have a pure function and you want to give it impure arguments (or any functor arguments, really) -- basically when you want to do what you specified in your question! <hr> The type signature of <code><$></code> is <pre><code>(<$>) :: Functor f => (a -> b) -> f a -> f b </code></pre> which means it takes a pure function (in this case <code>Node</code>) and a functor value (in this case <code>numberNode x</code>) and it creates a new function wrapped "inside" a functor. You can add further arguments to this function with <code><*></code>, which has the type signature <pre><code>(<*>) :: Applicative f => f (a -> b) -> f a -> f b </code></pre> As you can see, this is very similar to <code><$></code> only it works even when the function is wrapped "inside" a functor.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHaskell do notation to bind
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USkqr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThank you for mentioning this, I have no experience with applicatives but the concept looks awesome. It is just this kind of beautifull ways to solve problems I like about Haskell :) As I was asking for bind operator I will accept Gabriels answer, but I will definitely take a deeper look at this concept. Thank you very much for pointing this out to me =)
 singulars
 PostPostId
 PO
 UserUserId
 USfloAr

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.