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:
Is “support” for CLR extension methods planned before the release of
1.0?
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.) 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.
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:
Is “support” for CLR extension methods planned before the release of
1.0?
Also is CLR attribute support planned?
Cheers, Orion
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
But onto your roadmap questions: we don’t plan on supporting