Talk:Range modifications: Difference between revisions

m
forced a TOC (for now)
m (forced a TOC (for now))
 
(One intermediate revision by one other user not shown)
Line 1:
 
__TOC__
 
 
==Consistent with the goals of Rosetta Code ?==
These formulations are charmingly Procrustean and intemperate:
Line 15 ⟶ 19:
 
I've done similar. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 04:17, 24 October 2020 (UTC)
:Sadley I have no problem believing that. Did BoJo involve you in his world beating Covid app? Now -5 and -2 are both integers. Is -5--2 a valid range? How many of the 'hacks' implemented will make your unlucky customer less error prone?--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 15:17, 26 October 2020 (UTC)
 
On algorithm restriction: RC tasks must be succinct. I can't show huge extensive input but try and restrict this algorithm so it may work with such. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 04:17, 24 October 2020 (UTC)
Line 43 ⟶ 48:
:: Should an input of "10-25,1-5,27-30" quietly discard the "1-5"?
:: Is "3-1" a valid and necessary, or illegal and ignore-able or error-inducing input? --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 10:34, 24 October 2020 (UTC)
 
 
==Output quotes? ==
 
The example needs to be able to parse, modify and output the format. Showing normal language string literals is optional, but used in the task description start case as it more clearly shows the null string.
 
If your language idiomatically uses brackets or other methods to show string literals then that would be fine too. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 07:24, 25 October 2020 (UTC)
 
 
==Proposal:: Drop the two redundant (and Procrustean) bullet points==
 
The two Procrustean clauses ("''Solutions '''must''' work by XYZ ...''" "'''''Do not''' use algorithms that XYZ ...''") are redundant and contrary to the aims of Rosetta Code.