Timeline for Closed linked-list which uses sentinels to avoid passing itself
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2021 at 21:03 | vote | accept | Neil | ||
| Dec 3, 2018 at 19:38 | comment | added | Neil | Edited to show more of what's wrong with the 3rd option. | |
| Dec 3, 2018 at 19:24 | history | edited | Neil | CC BY-SA 4.0 |
"when I upcast" clarify.
|
| Dec 3, 2018 at 4:13 | vote | accept | Neil | ||
| Feb 27, 2021 at 21:03 | |||||
| Dec 3, 2018 at 4:12 | answer | added | Neil | timeline score: 0 | |
| Dec 3, 2018 at 0:00 | history | tweeted | twitter.com/StackCodeReview/status/1069380701001269248 | ||
| Dec 1, 2018 at 22:47 | answer | added | chux | timeline score: 4 | |
| Dec 1, 2018 at 20:45 | answer | added | Edward | timeline score: 4 | |
| Dec 1, 2018 at 17:47 | comment | added | Neil |
Good point; it doesn't matter in ListForEach because it has access to the list, but in general, I don't want to have the list as a separate argument. I want a closed solution that has access to every Link and List with a single pointer.
|
|
| Dec 1, 2018 at 17:31 | history | edited | Neil | CC BY-SA 4.0 |
Added static question.
|
| Dec 1, 2018 at 10:59 | comment | added | JS1 | I don't know what is wrong with the 3rd option you presented. You can prevent the list from "going round and round" by simply stopping when you reach the head of the list (which is passed in as an argument). | |
| Dec 1, 2018 at 6:08 | history | asked | Neil | CC BY-SA 4.0 |