Timeline for Performant Text File Reading in Scheme
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2023 at 17:38 | comment | added | J_H | Oh, sorry if I was unclear. I definitely meant to include Chibi in with scheme compilers. The technology has come a long way and I am accustomed to scheme and lisp compilers doing impressive things, on par with C compilers, if the app author gives them room to optimize. There's sort of two usual gotchas that can prevent that. Assigning mixed types to one identifier is a no no; I don't see that here. And then there is "list vs vector". In the reviewed code, the biggest thing I railed against was cons'ing up each character. Better to have a giant string, right? Or at least a string per line. | |
| Jan 15, 2023 at 15:51 | vote | accept | clartaq | ||
| Jan 15, 2023 at 15:50 | comment | added | clartaq | Thank you for the careful and insightful review. Clearly the title did not convey that I am looking for something with better performance. Enforcing the expected order of binding in #2 fixed that bug. It performs about the same as the others now. Some of the other methods I tried including reading big byte vector blocks, with no benefit. The comment about Scheme compilers is fair, but I really like chibi -- just read the standard and write your program. Thanks again. | |
| Jan 13, 2023 at 17:25 | history | edited | J_H | CC BY-SA 4.0 |
added 145 characters in body
|
| Jan 13, 2023 at 6:37 | history | edited | J_H | CC BY-SA 4.0 |
added 5 characters in body
|
| Jan 13, 2023 at 6:30 | history | edited | J_H | CC BY-SA 4.0 |
added 5 characters in body
|
| Jan 13, 2023 at 6:23 | history | edited | J_H | CC BY-SA 4.0 |
added 38 characters in body
|
| Jan 13, 2023 at 6:16 | history | answered | J_H | CC BY-SA 4.0 |