You can already say "foo _1.2.3_ bar". That said, I see little benefit in making rubygems bundler-aware, and I think it would constrain both projects in undesirable ways. For example, you propose rubygems checking for a…
Thanks for the props. The other operators are still supported as/is and don't cause the warning that == does.
RSpec 2 introduced an eq matcher so you can do this warning free: i.porkchop_sandwiches.count.should eq(1). Then for object identity you can still use be: i.porkchop_sandwiches.first.should be(my_sandwich) This is…
You can already say "foo _1.2.3_ bar". That said, I see little benefit in making rubygems bundler-aware, and I think it would constrain both projects in undesirable ways. For example, you propose rubygems checking for a…
Thanks for the props. The other operators are still supported as/is and don't cause the warning that == does.
RSpec 2 introduced an eq matcher so you can do this warning free: i.porkchop_sandwiches.count.should eq(1). Then for object identity you can still use be: i.porkchop_sandwiches.first.should be(my_sandwich) This is…