I’ve just uploaded a new beta that allows this to work. Add the following attribute to the libraries whose internals you want LINQPad to access: [assembly: InternalsVisibleTo(“LINQPadQuery”)] You’ll also need to enable this feature in LINQPad’s preferences (Edit | Preferences | Advanced). Let me know how you get along.
isn’t this illegal in C#? If “int” is only alias for “Int32” it should fail to compile with error CS0523. Is there some magic in the compiler? Yes; the error is deliberately suppressed in the compiler. The cycle checker is skipped entirely if the type in question is a built-in type. Normally this sort of … Read more
It sounds like you want to know more about the rationale behind the design of the language, rather than internals. “internals” to me means things like how objects are laid out in memory, how reference counting works, and so on. If you’re looking for a deeper understanding of the design decisions, try reading the PEPs: … Read more
The suggested fix message uses a const/static field for the assembly name: [assembly: InternalsVisibleTo(InternalsVisible.ToDynamicProxyGenAssembly2)] You used a string which does not correspond to the assembly name: [assembly: InternalsVisibleTo(“InternalsVisible.DynamicProxyGenAssembly2”)] Change it to: [assembly: InternalsVisibleTo(“DynamicProxyGenAssembly2”)] You can see the actual assembly name (which should appear in InternalsVisibleTo) in your error message: Type ‘Castle.Proxies.IReminiscenceableDataTableProxy’ from assembly ‘DynamicProxyGenAssembly2 (…)
Summary: Git’s pack files are carefully constructed to effectively use disk caches and provide “nice” access patterns for common commands and for reading recently referenced objects. Git’s pack file format is quite flexible (see Documentation/technical/pack-format.txt, or The Packfile in The Git Community Book). The pack files store objects in two main ways: “undeltified” (take the … Read more
I asked some people in the .Net team about this. QCalls are calls to native methods within the CLR runtime. They behave like other [DllImport]s, but they’re faster because they make specific (undocumented) assumptions about what the native methods do, so they can skip various marshalling and GC and exception checks. InternalCall is different; it’s … Read more
What does a database actually do to find out what matches a select statement? To be blunt, it’s a matter of brute force. Simply, it reads through each candidate record in the database and matches the expression to the fields. So, if you have “select * from table where name=”fred””, it literally runs through each … Read more
You should use factors. Yes they can be a pain, but my theory is that 90% of why they’re a pain is because in read.table and read.csv, the argument stringsAsFactors = TRUE by default (and most users miss this subtlety). I say they are useful because model fitting packages like lme4 use factors and ordered … Read more
This is implementation-specific, but your interpreter is probably interning compile-time constants but not the results of run-time expressions. In what follows CPython 3.9.0+ is used. In the second example, the expression “strin”+”g” is evaluated at compile time, and is replaced with “string”. This makes the first two examples behave the same. If we examine the … Read more
The details of how a debugger works will depend on what you are debugging, and what the OS is. For native debugging on Windows you can find some details on MSDN: Win32 Debugging API. The user tells the debugger which process to attach to, either by name or by process ID. If it is a … Read more