Re: The mathematical name behind "unfold-right" in srfi-1
chansey97
(06 Jun 2020 09:12 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
Marc Nieper-Wißkirchen
(06 Jun 2020 11:39 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
John Cowan
(06 Jun 2020 19:07 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
Marc Nieper-Wißkirchen
(06 Jun 2020 19:23 UTC)
|
Total functional programming
Lassi Kortela
(06 Jun 2020 19:37 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
Marc Nieper-Wißkirchen
(06 Jun 2020 19:37 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
Marc Nieper-Wißkirchen
(06 Jun 2020 19:53 UTC)
|
Email threading styles
Lassi Kortela
(06 Jun 2020 20:20 UTC)
|
Re: Email threading styles
Arthur A. Gleckler
(06 Jun 2020 20:26 UTC)
|
Re: Email threading styles
Lassi Kortela
(06 Jun 2020 20:33 UTC)
|
Re: Email threading styles
Marc Nieper-Wißkirchen
(06 Jun 2020 20:42 UTC)
|
Re: Email threading styles
Arthur A. Gleckler
(06 Jun 2020 20:45 UTC)
|
Rescuing SRFI GitHub issues and PRs
Lassi Kortela
(06 Jun 2020 20:50 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
John Cowan
(06 Jun 2020 20:55 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Arthur A. Gleckler
(06 Jun 2020 21:14 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
John Cowan
(06 Jun 2020 21:17 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Arthur A. Gleckler
(06 Jun 2020 21:39 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Arthur A. Gleckler
(06 Jun 2020 21:02 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Lassi Kortela
(06 Jun 2020 21:06 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Göran Weinholt
(07 Jun 2020 10:25 UTC)
|
Re: Rescuing SRFI GitHub issues and PRs
Arthur A. Gleckler
(07 Jun 2020 15:33 UTC)
|
Re: Email threading styles
Lassi Kortela
(06 Jun 2020 21:17 UTC)
|
Re: Email threading styles
Arthur A. Gleckler
(06 Jun 2020 21:37 UTC)
|
Re: Email threading styles
Marc Nieper-Wißkirchen
(06 Jun 2020 20:28 UTC)
|
Re: Email threading styles Lassi Kortela (06 Jun 2020 20:38 UTC)
|
Re: Email threading styles
Marc Nieper-Wißkirchen
(06 Jun 2020 20:48 UTC)
|
Re: Email threading styles
Lassi Kortela
(06 Jun 2020 20:56 UTC)
|
Re: Email threading styles
Arthur A. Gleckler
(06 Jun 2020 20:58 UTC)
|
Re: The mathematical name behind "unfold-right" in srfi-1
Marc Nieper-Wißkirchen
(06 Jun 2020 20:18 UTC)
|
> Well, this post of yours has shown me that the problem is more > complicated. Because in this case, it was probably the Right Thing :) > to start a new thread instead of adding this post of yours to the one > discussing category theory and other nonsense. One could start a new thread from scratch (with no parent message). But if the new conversation is an offshoot of the old one, that information would not be recorded. > As long as you reply to the most reasonable post, the flat list still > gets a nice tree structure: > https://srfi-email.schemers.org/srfi-discuss/threads/2020/06/ > > But it still allows for newcomers to read through all posts sequentially. > > (An unfortunate counter-example is what has happened on the SRFI 177 > lists: I think it is extremely hard for a newcomer to understand the > timeline of the discussion and, probably, the discussion as well.) I agree. The big trees can become almost unreadable. Hacker News (news.ycombinator.com) and similar platforms also organize the comments into trees, and have the same problem. I've tried to solve it for email by changing the subject line often. Even big trees remain surprisingly readable if sub-discussions change the subject. It's easy to forget to change it but any change is better than nothing when it comes to readability :)