Anonymous user
Talk:Range modifications: Difference between revisions
→Consistent with the goals of Rosetta Code ?: Yep.
Line 11:
: I must admit I ''was'' slightly taken aback by imm. slapping Wren got for "[ ]", esp. as the task does ''not'' specify output.
: Another concern is whether modified ranges ''should'' be held as a string, or something more native/useable. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 22:22, 23 October 2020 (UTC)
Think of an expensive design automation tool needing time and money to run. To apply a patch to the design, the documented flow amounts to a timely and costly rerun, or, a hack to an internal file of this format. The customer normally manually hacks, but while waiting for the vendor to decide on its support, can can make the hack even less error prone and present the vendor with an example of the requested functionality.
I've done similar. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 04:17, 24 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)
| |||