diff options
| author | Xavier Noria <fxn@hashref.com> | 2013-12-28 19:59:52 +0100 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2013-12-28 20:03:38 +0100 |
| commit | 126dc47665c65cd129967cbd8a5926dddd0aa514 (patch) | |
| tree | a8d162817929a8e2f33350c69c8f1d65b1d6234f /activerecord/lib/active_record | |
| parent | 7b8944681f9575b9b25a540b78a99bd80853553b (diff) | |
| download | rails-126dc47665c65cd129967cbd8a5926dddd0aa514.tar.gz rails-126dc47665c65cd129967cbd8a5926dddd0aa514.tar.bz2 rails-126dc47665c65cd129967cbd8a5926dddd0aa514.zip | |
blank? and present? commit to return singletons [Xavier Noria & Pavel Pravosud]
The contract of blank? and present? was in principle to return Object, as we
generally do, the test suite and description was consistent with that, but some
examples had comments like "# => true".
This cannot be unclear, we either fix the examples, or update the contract.
Since users may be already assuming singletons due to the examples and the fact
that they were returned before 30ba7ee, the safest option seems to be to revise
the contract and the implementation of String#blank?
The motivation for 30ba7ee was to improve the performance of the predicate, the
refactor based on === is on par regarding speed.
With this commit we start documenting return types using YARD conventions. We
plan to document return types gradually.
Diffstat (limited to 'activerecord/lib/active_record')
0 files changed, 0 insertions, 0 deletions