Anonymous user
Talk:Search a list of records: Difference between revisions
→Overhauled task: mention that the page has been taken out of draft status
(→Long Line: Ta.) |
(→Overhauled task: mention that the page has been taken out of draft status) |
||
| (7 intermediate revisions by 2 users not shown) | |||
Line 55:
::::::: I wonder if that would take us from the simplest 'first match' of functions like JS's '''.indexOf(), .find()''', and '''.findIndex()''', into a broader database query ? Perhaps there's an argument for restricting the scope a little ? Not sure … [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 20:21, 11 October 2015 (UTC)
:::::::: Normally, in all my professional travels in computer-land, I found that most users want to know ''all'' the cities whose (say) population is under five million, not just the first city in the list --- which depends on, in most cases for this Rosetta Code task, when each entry (city) was built/constructed (first come, first served, er, ··· first found). That's something most people don't care about or even know in which order the cities (entries) were "entered" (constructed). But, the task requirements are what they are. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:40, 22 August 2016 (UTC)
::::::::: Both finding the first match in a list, and finding all matches, are sometimes useful in practice. You're right that the data set in this task is not the best example of a useful scenario for finding the first match only, but I thought that replacing it with a different data set would be too invasive a change, so I left it as-is.
::::::::: I don't know if there's already a task for finding all matches in a list... If not, I think it should be created as a separate task under the name "'''Filter a list'''". --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 04:58, 23 August 2016 (UTC)
==Long Line==
Line 62 ⟶ 67:
==Grep redirect==
Grep is used for many things in programming - it is a major posix Unix command for example. I don't think it is wise to forward Grep to this task. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 12:56, 3 December 2015 (UTC)
==Overhauled task==
I've completely rewritten the task description. It should be of much higher quality now, without invalidating existing solutions much (and I've added notice templates where solutions do need updating). I've also renamed the page from "'''Array search'''" to "'''Search a list of records'''", to better represent what it is about and to make it consistent with the existing [[Search a list]] task.<br>
:: Make sure that other Rosetta Code tasks that refer to this one (via '''Related tasks''' links --- or the new ''' See also''' being implemented via some overhauling). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:26, 22 August 2016 (UTC)
::: Yes, I took care of that when moving the page. --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 04:52, 23 August 2016 (UTC)
I think in this form it's ready to be taken out of draft status, but I'll wait a while to see if people have any objections, or issues while updating to the new task description.<br>
--[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 10:48, 22 August 2016 (UTC)
: It shouldn't be taken out of draft task until most of the programming entries conform to the new and/or changed task requirements and give those programmers a chance to comply and/or comment on the changes and new requirement(s). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:21, 22 August 2016 (UTC)
:: Taking it out of draft status now, as two thirds of the entries already fulfill the updated task description (and the rest basically just need the 3rd test-case added, which should be simple enough). --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 12:22, 27 August 2016 (UTC)
: Also, I much prefer (for this task and other tasks being changed) the old form of the task's preamble where all the section headers are in '''bold''' (which makes it much easier to find the relevant sections). Also, I think all those <small> [edit] </small> thingys just obscure the readability of the task's preamble. If somebody wants to edit the task's requirement(s), description, related tasks, examples, etc., they can use the <big> ''Edit'' </big> tab entry (at the top, just like always). There's no need to provide an individual <small> [edit] </small> button (an HTML field thingy) for each section individually. Having five <small> [edit] </small> thingys (for this task) interferes with the perusing of the task's preamble. Also, most '''Related task(s)''' section headers have been changed to '''See also''' section headers when using the new format. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:21, 22 August 2016 (UTC)
:: Let's take this discussion to [[Template_talk:Task_heading]]. --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 04:52, 23 August 2016 (UTC)
| |||