Aaron Hill
Aaron Hill
I believe we already do those coercions (based on the type declared in the signature) in the Activation code that sets up a method call.
> So even if you want an f64 in rust, even after AVM-layer coercions, you still need to handle both Value::Integer and Value::Number. I think the vast majority of native...
This should be fixed on the latest SpongeForge
Can you open an issue on the SpongeForge issue tracker?
@redhotvengeance: Sorry, I forgot about this for a little bit :smile:. I'm still having some problems with Rubinius. I've tried asking on `#rubinius` on Freenode, but they weren't able to...
@redhotvengeance: It's not that the tests aren't passing, it's that they're being skipped because a gem isn't being loaded. I'm working to fix it.
@redhotvengeance: If you look at [this job](https://travis-ci.org/redhotvengeance/deep_thought/jobs/16552696#L842), you'll notice that only 41 tests have run (there should be 52). On [this line](https://travis-ci.org/redhotvengeance/deep_thought/jobs/16552696#L747), you'll see that the `zlib` library isn't being...
What's the status of this PR? This would be very useful for Ruffle
A simplified example that gives a similar error: ```rust struct Foo; fn mut_ref(val: &'a mut &'b mut Foo) { let tmp: &'b mut Foo = *val; } ``` Gives the...
Calling `Xml.copy()` actually looks at some of the XML settings: https://github.com/adobe/avmplus/blob/858d034a3bd3a54d9b70909386435cf4aec81d21/core/E4XNode.cpp#L713-L716