Talk:Range modifications: Difference between revisions
→Proposal:: Drop the two redundant (and Procrustean) bullet points
Line 53:
:Specifying an algorithm to use is done on many tasks. You are given potentially more freedom here as you are not restricted to a specific algorithm, just barred from what is a memory hungry approach for large ranges. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 13:09, 24 October 2020 (UTC)
::: "is done on" – examples ? They may need improvement too.
::: "barred from" (sic) – Where scope is seen for better approaches, variant drafts can illustrate them. There's no place on Rosetta code (the very raison d'etre of which is comparison of alternative approaches) for an appetite for "barring" approaches to solving a problem. Deletionary appetites are better satisfied elsewhere. This is not the place for them. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 14:09, 24 October 2020 (UTC)
| |||