It should be part of the documented public API, since we have an entire
section of the guides dedicated to it. Documented in a way that
addresses the concerns which kept it undocumented in the past.

7.0.0 was released on June 16, 2014

http://unicode-inc.blogspot.com.ar/2014/10/unicode-version-70-complete-text-of.html

ruby bin/generate_tables

added description for rails generators, and fixed sentence formation for active_support/notifications [ci skip]

/cc @chancancode

pattern removal

added example for string#remove and test case for remove of multiple occurence of pattern

removed extra whitespaces

- Reference : https://github.com/rails/rails/pull/17493#issuecomment-61739359
- Duration stopped inheriting from ProxyObject in https://github.com/rails/rails/pull/16574

- Russian time was changed to UTC+3 from UTC+4 recently. This broke the
  string_to_ext test.

This patch uniformizes warning messages. I used the most common style
already present in the code base:

* Capitalize the first word.

* End the message with a full stop.

* "Rails 5" instead of "Rails 5.0".

* Backticks for method names and inline code.

Also, converted a few long strings into the new heredoc convention.

The character "*" is unnecessary in option candidates.
This incorrect markup was injected in e8c9aeca .

This will avoid naming clash with user defined methods

The check for circular loading should depend on a stack of files being
loaded at the moment, rather than the collection of loaded files.

This showed up indirectly in #16468, where a misspelled helper would
incorrectly result in a circularity error message.

References #16468

@carlosantoniodasilva pointed out that when `@person` is nil then this would blow up when you ended up calling `#first`on `nil`.

> "there’s no way to break a try chain when you enter it :D"

[ci skip]

- better `if` example
- Added chaining example to the try method description
- Documented the `respond_to?` check to the try method description
- Clearer wording to explain that argument error is raised on argument mismatch to responding method, rather than to non-responding method (which is handled without exception by `try`)
- `.any?` is more precise than `! .blank?`
 - Don't need to use `try` on `children` as (for regular associations) they will always be a collection or array that responds to `first`
- Fix typos/grammar

Based on commit 5e51bdda.

Replace (slower) block.call with (faster) yield