You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title is a mouthful, but the basic issue is that if a module is included, then modified by including other modules into itself, then included again, the new includes don't get spliced into the target hierarchy correctly.
The following example shows that the order of modules is different from MRI:
Output:
[--dev]
~/projects/jruby $ rvm ruby-2.1 do ruby blah.rb
in Z
in A
in Q
[--dev]
~/projects/jruby $ jruby blah.rb
in A
in Z
in Q
Title is a mouthful, but the basic issue is that if a module is included, then modified by including other modules into itself, then included again, the new includes don't get spliced into the target hierarchy correctly.
The following example shows that the order of modules is different from MRI:
Output:
Script:
This is the likely cause of Compass/compass-rails#179.
The text was updated successfully, but these errors were encountered: