# IronRuby 0.9.1

**URL:** <https://www.ruby-forum.com/t/ironruby-0-9-1/176389>\
**Category:** IronRuby\
**Created:** [September 30, 2009, 12:06am UTC](https://www.ruby-forum.com/t/ironruby-0-9-1/176389 "2009-09-30T00:06:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Orion\_E](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/65b543/32.png) [@Orion\_E](https://www.ruby-forum.com/u/Orion_E)\
**Post date:** [September 30, 2009, 12:06am UTC](https://www.ruby-forum.com/t/ironruby-0-9-1/176389/1 "2009-09-30T00:06:49Z")

</div>

Congrats on the release! It solves a few of the bugs I’ve encountered  
and  
overall seems a bit faster which is always good. It’s getting really  
nice to  
use these days. We are using it internally for automated UI testing with  
White, and have got our QA people writing IronRuby scripts, which they  
are  
really happy with 🙂  
I just have a couple of minor roadmap questions:

1. Is “support” for CLR extension methods planned before the release of  
1.0?
2. Also is CLR attribute support planned?

Cheers, Orion

---

<div class="post-metadata">

**Author:** ![Orion\_E](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/65b543/32.png) [@Orion\_E](https://www.ruby-forum.com/u/Orion_E)\
**Post date:** [September 30, 2009, 12:43am UTC](https://www.ruby-forum.com/t/ironruby-0-9-1/176389/2 "2009-09-30T00:43:07Z")

</div>

Orion,

That’s great to hear, especially that writing Ruby scripts make people  
happy 🙂 But onto your roadmap questions: we don’t plan on supporting  
calling C# extension methods, or using CLR attributes in Ruby code.

For C# extension methods, it takes a ton of work to find extension  
methods, as IronRuby would have to scan every loaded assembly, and map  
those static extension methods back to the type you’d expect them to be  
on. It’s a feature where performance will only affect compile time, but  
at runtime would be very slow. In the meantime, a good work-around is to  
monkey-patch those extensions methods onto the correct types using Ruby.

CLR attributes are difficult because it would require a unique CLR type  
to be emitted for a type which uses CLR attributes; today we use a  
shared underlying CLR type for all Ruby types, unless a unique CLR type  
already exists (in the case where you inherit from a CLR type, implement  
an interface, etc). Today we suggest people create a stub type in C#  
which has the attributes, and then have your Ruby class inherit from  
that type. While this is a bit of a cop-out, libraries like  
IronRubyInline ([GitHub - rvernagus/IronRubyInline: Allows C#, Visual Basic, and F# to be written inline with IronRuby.](http://github.com/rvernagus/IronRubyInline)) can make it  
really easy to mix C# and Ruby code.

If you’d like more effort to be focused on these features for 1.0,  
please open a bug on codeplex (or find an already open bug) and vote on  
it.

~js

From: removed\_email\_address@domain.invalid  
[[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Orion E.  
Sent: Tuesday, September 29, 2009 2:57 PM  
To: removed\_email\_address@domain.invalid  
Subject: [Ironruby-core] IronRuby 0.9.1

Congrats on the release! It solves a few of the bugs I’ve encountered  
and overall seems a bit faster which is always good. It’s getting really  
nice to use these days. We are using it internally for automated UI  
testing with White, and have got our QA people writing IronRuby scripts,  
which they are really happy with 🙂

I just have a couple of minor roadmap questions:

1. Is “support” for CLR extension methods planned before the release of  
1.0?
2. Also is CLR attribute support planned?

Cheers, Orion