# Code Review: Types2

**URL:** <https://www.ruby-forum.com/t/code-review-types2/177800>\
**Category:** IronRuby\
**Created:** [October 23, 2009, 9:57pm UTC](https://www.ruby-forum.com/t/code-review-types2/177800 "2009-10-23T21:57:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\
**Post date:** [October 23, 2009, 9:57pm UTC](https://www.ruby-forum.com/t/code-review-types2/177800/1 "2009-10-23T21:57:17Z")

</div>

tfpt review “/shelveset:Types2;REDMOND\tomat”

DLR:  
The overload resolver should handle a candidate set with no callable  
method (e.g. have unbound generic parameter). Adds a BindingResult value  
that indicates such case.

Ruby, Python:  
Disables VSHost process in CLR4 configurations to enable debugging in  
VS2010. VS2010 doesn’t handle multiple TargetFrameworkVersions per  
project correctly when launching VSHost process.

Ruby:  
Simplifies ClsTypeEmitter and adds support for overriding default  
indexers.

Fixes [http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=2907:](http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=2907:)  
Previously, generic type definitions were handled as super-classes for  
their instantiations so that it is possible to add a Ruby method on a  
generic type definition and call it from any instantiation. This  
approach breaks when inheriting from a generic type - the inheritance  
hierarchy is incorrect. It makes more sense to treat generic type  
definitions as modules - they can’t be instantiated, don’t define any  
callable methods and we can mix them into their instantiations instead  
of inheriting from them.

Adds an overload to String.new that takes a byte[] and turns it into a  
binary string.

Implements a debug view from RubyMethod.

Tomas