Databases
StackOverflow2013
Postsdbo
POMake type's instances non-storable
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMake type's instances non-storable
    primarykey
    data
    text
    <ul> <li>Is there a way to mark a type (or even better, an interface) so that no instances of it can be stored in a field (in a similar way to <code>TypedReference</code> and <code>ArgIterator</code>)?</li> <li>In the same way, is there a way to prevent instances from being passed through anonymous methods and -- In general -- To mimic the behavior of the two types above?</li> <li>Can this be done through ILDasm or more generally through IL editing? Since <a href="http://code.google.com/p/unconstrained-melody/" rel="nofollow noreferrer">UnconstrainedMelody</a> achieves normally unobtainable results through binary editing of a compiled assembly, maybe there's a way to "mark" certain types (or even better, abstract ones or marker interfaces) through the same approach.</li> </ul> <p>I doubt it’s hardcoded in the compiler because the <a href="http://msdn.microsoft.com/en-us/library/t93xez96(v=vs.80).aspx" rel="nofollow noreferrer">documentation for the error CS0610</a> states:</p> <blockquote> <p>There are some types that cannot be used as fields or properties. These types include...</p> </blockquote> <p>Which in my opinion hints that the set of types like those can be extended -- But I could be wrong.</p> <p>I've searched a bit on SO and while I understand that <a href="https://stackoverflow.com/questions/6266031/c-sharp-net-how-to-throw-a-compiler-error">throwing a compiler error</a> programmatically can't be done, I could find no source stating that certain "special" types' behaviors couldn't be replicated.</p> <p>Even if the question is mostly academic, there could be some usages for an answer. For example, it could be useful sometimes to be sure that a certain object's lifetime is constrained to the method block which creates it.</p> <p><strong>EDIT:</strong> <code>RuntimeArgumentHandle</code> is one more (unmentioned) non-storable type.</p> <p><strong>EDIT 2:</strong> If it can be of any use, it seems that the CLR treats those types in a different way as well, if not only the compiler (still assuming that the types are in no way different from others). The following program, for example, will throw a <code>TypeLoadException</code> regarding <code>TypedReference*</code>. I've adapted it to make it shorter but you can work around it all you want. Changing the pointer's type to, say, <code>void*</code> will not throw the exception.</p> <pre><code>using System; unsafe static class Program { static TypedReference* _tr; static void Main(string[] args) { _tr = (TypedReference*) IntPtr.Zero; } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMir
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMake type's instances non-storable
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMake type's instances non-storable
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMake type's instances non-storable
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI wouldn't be at all surprised if it *were* hard-coded, btw. Just because the documentation doesn't want to pin it down doesn't mean that's not the way it's done in the compiler.
      singulars
      1. POMake type's instances non-storable
      1. USJon Skeet
    2. COI think the same thing, but I'll have to check.
      singulars
      1. POMake type's instances non-storable
      1. USKendall Frey
    3. CO[CS0611](http://msdn.microsoft.com/en-US/library/bfca7x6z(v=vs.80).aspx) is a related error, although probably the solution to either would apply to both.
      singulars
      1. POMake type's instances non-storable
      1. USMir
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload