It's sometimes hard to quickly find where deprecated call was performed, especially in case of migrating between Rails versions. So this is an attempt to improve the call stack part of the warning message by providing caller explicitly.
Provide a call stack for deprecation warnings where needed.
Doesn't caller have a pretty big performance overhead? Even if it does, I don't know if it's enough to matter. Just wondering.
@carlosantoniodasilva maybe this solution will be more clear and full? #6107
@steveklabnik maybe we could try benchmarking it to see? Also, we hope people fix warnings as soon as they see them, killing the possible existent overhead.
@gazay perhaps, I'll check and ask someone else to do so, thanks for pointing that out!
@gazay @carlosantoniodasilva yep, rails/rails#6107 seems better in this case 👍