Talk:Longest increasing subsequence: Difference between revisions
Content added Content deleted
(→Naming the methods: My thoughts...) |
(→Splitting in two subtasks?: new section) |
||
Line 9: | Line 9: | ||
:Hi Grondilu, I would want to mention at least an abbreviation of the language name in my subheadings directly below my header line as that way if someone makes an edit later, the Summary points directly at the language+sub-heading, making it easier to locate an edit on a large page. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 05:19, 18 August 2013 (UTC) |
:Hi Grondilu, I would want to mention at least an abbreviation of the language name in my subheadings directly below my header line as that way if someone makes an edit later, the Summary points directly at the language+sub-heading, making it easier to locate an edit on a large page. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 05:19, 18 August 2013 (UTC) |
||
== Splitting in two subtasks? == |
|||
What about splitting this in: |
|||
* [[Longest increasing subsequence/Dynamic programming]] |
|||
* [[Longest increasing subsequence/Patience sorting]] |
|||
? |
|||
--[[User:Grondilu|Grondilu]] ([[User talk:Grondilu|talk]]) 09:34, 18 August 2013 (UTC) |
Revision as of 09:34, 18 August 2013
Naming the methods
In order to avoid long subsection titles, I suggest:
- not mentioning the programming language again
- using dynamic programming and patience sorting as names
--Grondilu (talk) 04:39, 18 August 2013 (UTC)
- Hi Grondilu, I would want to mention at least an abbreviation of the language name in my subheadings directly below my header line as that way if someone makes an edit later, the Summary points directly at the language+sub-heading, making it easier to locate an edit on a large page. --Paddy3118 (talk) 05:19, 18 August 2013 (UTC)
Splitting in two subtasks?
What about splitting this in: