StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2948364
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-06-01T08:50:59.707
FavoriteCount
0
LastActivityDate
2010-06-01T09:06:42.447
LastEditDate
2010-06-01T09:06:42.447
LastEditorUserId
183828
OwnerUserId
183828
ParentId
2948205
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
V2 uses standard accumulating variable to get tail recursion done: <pre><code>loop ([0;1;2;3;4;5;6;7;8], []) -> loop ([3;4;5;6;7;8], [(0,1,2)]) -> loop ([6;7;8], [(3,4,5), (0,1,2)]) -> loop ([], [(6,7,8), (3,4,5), (0,1,2)]) -> [(6,7,8), (3,4,5), (0,1,2)] </code></pre> V3 uses <a href="http://en.wikipedia.org/wiki/Continuation_passing_style" rel="noreferrer">continuation</a>, or in plain English, an accumulating function: <pre><code>loop ([0;1;2;3;4;5;6;7;8], x->x) -> loop ([3;4;5;6;7;8], x->(0;1;2)::x) -> loop ([6;7;8], x->(3;4;5)::x) -> loop ([], x->(6,7,8)::x) -> [(6,7,8)] // x->(6,7,8)::x applies to [] -> [(3,4,5);(6,7,8)] // x->(3,4,5)::x applies to [(6,7,8)] -> [(0,1,2);(3,4,5);(6,7,8)] // x->(0,1,2)::x applies to [(3,4,5);(6,7,8)] </code></pre> You can see the difference between accumulating variables and accumulating functions: Using accumulating variables stops at the last call as the accumulating variable stores the answer. However, the accumulating function still does some backtrack work after the last call. It should be noticed that using accumulating functions is indeed tail recursive as the recursive call <code>loop t (fun ls -> accfun ((a,b,c)::ls))</code> is actually the last statement of this function. Btw, the code you provided is a good example to show the concept tail recursive functions. One way to understand these sample code is to work on small cases as I did in the above two illustrations. After working on some small cases, you will understand the concept deeper. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnderstanding F# tail-recursive
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USYin Zhu
UserOwnerUserId
1. USYin Zhu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUnderstanding F# tail-recursive
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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 very much. your answer is great
 singulars
 PostPostId
 PO
 UserUserId
 USkev

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.