remove redundant var
remove variable and fix warning
Merge pull request #10536 from vipulnsward/fix_exp_warning

remove variable and fix warning
Merge pull request #10535 from vipulnsward/remove_var

remove redundant var
sort => sort! on new array
[ci skip] document protect_against_forgery? method
Merge pull request #10510 from think602/master

[ci skip] document protect_against_forgery? method
Set the inverse when association queries are refined

Suppose Man has_many interests, and inverse_of is used.

Man.first.interests.first.man will correctly execute two queries,
avoiding the need for a third query when Interest#man is called. This is
because CollectionAssociation#first calls set_inverse_instance.

However Man.first.interests.where("1=1").first.man will execute three
queries, even though this is obviously a subset of the records in the
association.

This is because calling where("1=1") spawns a new Relation object from
the CollectionProxy object, and the Relation has no knowledge of the
association, so it cannot set the inverse instance.

This commit solves the problem by making relations spawned from
CollectionProxies return a new Relation subclass called
AssociationRelation, which does know about associations. Records loaded
from this class will get the inverse instance set properly.

Fixes #5717.

Live commit from La Conf! :sparkles:
Merge pull request #10543 from vipulnsward/to_sort

Can you improve the commit message a little bit? It's good to describe why the change is happening.