I find it amazing that Edwin Brady wrote Idris2 on Chez without even knowing that scheme has records

@screwtape @ldbeth @galdor @svetlyak40wt was thinking sticking to lisp(s) in general might generate some likewise-applicable responses, but wanted to limit it to #lisp so that things don't stray too far off into the well-trodden #gdb debugging discourse

What are some ideal bugs for teaching lisp debugging?

@screwtape @ldbeth @galdor @svetlyak40wt

I think that #java's massive infrastructure overhaul to include continuations will pay off for them and prove the continuation hypothesis true ;)

@ekaitz_zarraga what I do whenever I'm digging into a subject is to go ahead and steal all the books on the subject as epubs, keeping them in their own directory and then grep the dir religiously. search engines are pretty much useless these days.

@ekaitz_zarraga I've been reading "C++20 The Complete Guide" which is a good overview; I'd say it really comes down to is making heavy use of ranges and views with pipelines; it leads to more functional code that is generally safer. Also spans are an intuitive way of more-safely doing things you'd use pointers for while enforcing a degree of safety.

Theres still lots of little gotchas, but grepping the book has shown that it does a pretty good job of finding and documenting them. Overall, 20 seems to provide a lot of facilities to do much more safe C++ programming with common patterns of composition from fp, eliminating a fair amount of C++ induced anxiety

Bjarne Stroustrup's talk on C++ 2006-2020 @ #HOPL IV is good because it takes you from the #cpp that you remember and hate (98-11), up to the solutions they devised to tame the complexity in C++20

https://www.pldi21.org/prerecorded_hopl.5.html

ok, just here me out...

#lisp #cpp

"Naming your functions is one of the hardest aspects of #programming"
-- those-who-dont-use-lisp-kebab-conventions

(in #lisp naming is easy, just describe the function lol)