docs(Iter): keep deprecated message more simple,

[illusory0x0]

Iter::singleton(a) + self is more clear than [a].iter() + self and conforms to the conventions of other programming languages.

[peter-jerry-ye-code-review]

Deprecation message standardization for iterator operations

Category
Maintainability
Code Snippet
#deprecated("Use [a].iter() + self or Iter::singleton(a) + self instead")
#deprecated("Use self + [a].iter() or self + Iter::singleton(a) instead")
Recommendation
Keep only the Iter::singleton(a) suggestion as shown in the changes
Reasoning
Having a single recommended way to perform an operation improves code consistency and reduces confusion. The Iter::singleton(a) approach is more idiomatic and clearer in expressing the intent compared to creating a single-element array and converting it to an iterator.

More efficient iterator creation with singleton

Category
Performance
Code Snippet
[a].iter() vs Iter::singleton(a)
Recommendation
Continue encouraging Iter::singleton(a) usage
Reasoning
Using Iter::singleton(a) directly creates an iterator without the overhead of creating a temporary array first, making it potentially more efficient than [a].iter()

Documentation update suggestion

Category
Maintainability
Code Snippet
/// Returns a new iterator with the element a prepended to the original iterator.
Recommendation
Add an example showing the recommended usage with Iter::singleton in the method documentation
Reasoning
Including examples of the recommended alternative directly in the documentation helps users migrate away from deprecated methods more effectively

[coveralls]

Pull Request Test Coverage Report for Build 118

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 89.361%

---

Totals
Change from base Build 104:	0.0%
Covered Lines:	3452
Relevant Lines:	3863

---

💛 - Coveralls