StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15159347
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-01T13:50:52.620
FavoriteCount
0
LastActivityDate
2013-03-01T13:50:52.620
LastEditDate
LastEditorUserId
0
OwnerUserId
33518
ParentId
15150157
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
The F# type checking mechanism is more strict than the type checking in C# in a number of ways. One aspect of this is that F# does not do any implicit conversions behind the scenes and so you have to use the right numeric literals (like <code>1.0f</code>) or explicit conversion functions (like <code>float32</code>). Why is the language designed in this way? One reason is that it makes type inference simpler and more predictable. For example: <pre><code>let data = [| 0; 1; 2 |] let writeData n = data.[0] <- n </code></pre> Here, the F# compiler knows that <code>data</code> is of type <code>int[]</code> (because it is initialized to an array containing integers). It also knows that <code>writeData</code> is a function <code>int -> unit</code> because the array contains integers and so <code>n</code> has to be an integer too. If the compiler did implicit conversions, there would be a lot of uncertainties: <ul> <li><code>data</code> could be, for example, <code>float[]</code> or <code>float32[]</code> because you could implicitly convert the integers to other numeric types</li> <li><code>dwriteData</code> could take any numeric type that is convertible to <code>int</code> (such as <code>int16</code>, <code>sbyte</code> etc.)</li> </ul> This would make the type information a lot more complicated and you'd probably have to specify types explicitly more often. For this reason, F# chooses a tradeoff - you have to write conversions explicitly, but then you do not need to use type annotations as often.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConversion differences between C# and F# using same library
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTomas Petricek
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConversion differences between C# and F# using same library
 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
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.