StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12829073
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-10-10T21:58:16.577
FavoriteCount
0
LastActivityDate
2012-10-10T22:38:51.470
LastEditDate
2012-10-10T22:38:51.470
LastEditorUserId
561186
OwnerUserId
561186
ParentId
12827869
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
As far as I can understand in this case <code>Foo<T></code> is an open unbound generic type, so at runtime the CLR will use it as a blueprint/skeleton to construct and close a generic type with the type parameter type specified (<code>Foo<int></code>, <code>Foo<object></code>, etc.). So basically <code>Foo<int></code> is a runtime constructed implementation of the <code>Foo<T></code> skeleton. Now, at run-time you can get the type of <code>Foo<int></code> either by using <code>typeof(Foo<int>)</code> or <code>typeof(Foo<>).MakeGenericType(new[] { typeof(int) })</code> and it's not the same <code>Type</code> and it wouldn't make sense for it to be. But look closer and you will see that both <code>typeof(Foo<T>)</code> and <code>typeof(Foo<int>)</code> share the same metadata token and GUID. Another interesting thing is that <code>typeof(Foo<int>).Assembly</code> will be what you would expect, but as you've noticed already you can't get that type from the Assembly. That's because <code>Foo<int></code> is not defined in the assembly (you can check the assembly metadata with Reflector/ILSpy). At run-time the CLR will create ("construct") a specialized ("closed") version of the <code>Foo<T></code> for <code>Foo<int></code> (so - constructed closed type of an unbounded open generic type definition) and "give" it a <code>Type</code>. So unless the CLR exposes directly somehow the list of closed generic types it generates at run-time you are out of luck. Also here is a snippet that might confirm what I am saying: <blockquote> Even though each construction of a generic type, such as Node< Form > and Node< String >, has its own distinct type identity, the CLR is able to reuse much of the actual JIT-compiled code between the type instantiations. This drastically reduces code bloat and is possible because the various instantiations of a generic type are expanded at run time. All that exists of a constructed type at compile time is a type reference. When assemblies A and B both reference a generic type defined in a third assembly, their constructed types are expanded at run time. This means that, in addition to sharing CLR type-identities (when appropriate), type instantiations from assemblies A and B also share run-time resources such as native code and expanded metadata. <a href="http://msdn.microsoft.com/en-us/magazine/cc163683.aspx">http://msdn.microsoft.com/en-us/magazine/cc163683.aspx</a> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POList closed types that runtime has created from open generic types
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIvan Zlatev
UserOwnerUserId
1. USIvan Zlatev
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POList closed types that runtime has created from open generic types
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThis is some heavy "run-time CLR magic": the static constructor of Foo<T> is called for each closed type "loading" :-) P.S. Where is Skeet when you need him?
 singulars
 PostPostId
 PO
 UserUserId
 USM.A. Hanin

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.