Standard libraries?
Should the cookbook include sections on semi-standard libraries? I was thinking:
Seriesby Richard Waters. It seems to have almost become part of the CL standard, and close to Haskell's lazy lists (but with less core language integration)Iterate, as there is a page onloopAnaphora
What about the link to Awesome-CL coming in 2nd position in the front page's Other Resources ? It plays this role to me, however I'd move the section up before "further remarks" (and also move the old "contributors" list into a file and remove it from the front page).
on these libs, I'd rather add examples than another list.
- the loop page is a bit scarce, I'd add iterate (and for) examples on it too
- never used Anaphora
- never used Series too, even if I saw it. It is living-dead, under-documented (even though this github wiki looks better) and with unusual function names, so I'd be surprised this one is semi-standard, but that would be nice.
I agree that a "Popular"/"Common"/"Unofficially standard" library section would be useful.
@vindarel did we close this issue?
I'll let you both close, I am myself not convinced by the utility of this but it seems you too are.
Or we close when we add content about Iterate and Series in the loop section and Anaphora where appropriate.
We forgot Alexandria. https://common-lisp.net/project/alexandria/draft/alexandria.html It has helper functions about different things: hash tables, sequences, IO, macro writing… the approach used in the cookbook so far is to give recipes per topics, so I'd reference Alexandria in the corresponding sections, as it is done in Data Structures. (instead of presenting Alexandria generally in one single section if that's the idea)
Happy to close; I don't think my original question/issue was specific enough. I was mainly curious about the criteria for using a library in cookbook recipes. To what extent is it the job of this cookbook to replace what should be in a library's manual?
mmh replace ? I don't think we replace. We illustrate, we gather content from several sources, we show the builtt-in way and an useful library side to side,… do you have an example ? (anyway, IMO as long as someone writes Lisp documentation that's great)