StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3541031
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-08-22T10:04:23.160
FavoriteCount
0
LastActivityDate
2010-08-22T10:04:23.160
LastEditDate
LastEditorUserId
0
OwnerUserId
19299
ParentId
3539400
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I haven't looked closely at the algorithm/logic, but here is how I would touch it up: <pre><code>let rec pathFind (area:map,start, goal, openNodes:PathingNode list, closedNodes:PathingNode list)= let rec checkNeighbours (opn, neighbours) = match neighbours with | [] -> opn | hd::tl -> if List.exists (fun x -> x.point = hd.point && x.f > hd.f) opn then checkNeighbours(remove opn (fun x -> x.point = hd.point), tl) elif not(List.exists (fun x -> x.point = hd.point) closedNodes) && not(List.exists (fun x -> x.point = hd.point) opn) then checkNeighbours({hd with parent = Some(openNodes.Head)}::opn, tl) else checkNeighbours(opn, tl) let neighbours = area.GetNeighboursOf(openNodes.Head.point) |> List.map (fun mp -> nodeToPathNode(mp, openNodes.Head, goal)) |> List.filter (fun pnd ->pnd.point.value = 0) let openLocalNodes = checkNeighbours(openNodes.Tail, neighbours) if List.exists (fun x -> x.point = goal) openLocalNodes then {point=goal; h=0; g=goal.Distance(start); parent=Some(openNodes.Head)} else pathFind(area, start, goal, openLocalNodes, openNodes.Head::closedNodes) </code></pre> <code>PathingNode</code> - types begin with capital letters (<code>list</code>/<code>option</code>/<code>array</code>/<code>ref</code> are the only exceptions). Whitespace after every comma, semicolon, or vertical bar. Lessen indent after <code>hd::tl</code> line, and use <code>elif</code> rather than <code>else if</code>. Get rid of lots of unneeded parentheses (<code>f x</code> not <code>f(x)</code>, <code>if cond then</code> not <code>if(cond) then</code>). Pipelining style a little more (<code>let neighbours=...</code>). Otherwise, at a glance this looks good.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POA little help F-Sharping up this path-finding code, please
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBrian
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POA little help F-Sharping up this path-finding code, please
 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
 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
 VTAcceptedByOriginator
CommentsPostId
1. COThanks Brian, that's just the kind of stuff I was after :¬)
 singulars
 PostPostId
 PO
 UserUserId
 USjdoig

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.