These are chat archives for opal/opal
element.$name()is undefined (which is the code on line 21). the only way i can see to bypass this error is to do something like this: http://cl.ly/1I2O1t3X0W0O. however, i'd prefer to find a solution for this in native opal. does anyone have any ideas?
does that give a significant performance improvement?
@ryanstout only on math ops, on that it's dramatic, it's the difference between method call with proto chain lookup and func call (which is substantially inlined by all browsers)
bundle exec rake ???
compiler_option :inline_operators, true, :as => :inline_operators?, I am seeing 4 errors for the entire spec suite, in
String#+. Are those the failures you are referring to? Is there anything else?
rake mspec_phantomwhich uses phantomjs and sprockets to run the specs, just to add a different code path
brew install phantomjs-ing now. I'll try to wrap my mind around it over the weekend.
$ bundle exec rake mspec_phantom Starting MSpec Runner... [filters] Adding 43 spec files... [shared] Adding 160 spec files... [lexer] Adding 1 spec files... [parser] Adding 30 spec files... [rubyspecs] Adding 298 spec files... Thin web server (v1.6.3 codename Protein Powder) Maximum connections set to 1024 Listening on localhost:9999, CTRL+C to stop TypeError: undefined is not an object (evaluating 'args') /Users/vais/GitHub/opal/lib/mspec/opal/sprockets.js:34 in global code
rake mspec_phantomwork for you?
@adambeynon Got a quick question on Promises, not sure if I'm doing something wrong or ran into a limitation. I'm trying to run some code whether the promise is resolved or rejected, for instance in an HTTP request via opal-query:
HTTP.get('/fooling/jsonstest').then do alert 'good!' end.fail do alert 'oops!' end.always do alert 'finished' end
But the "always" block doesn't actually happen always. My expectation would be to get "good!" + "finished" alerts if the request was successful, and "oops!" + "finished" alerts if not. Any ideas?