This is broken, but the stack limit feature works. Some debugging needed.
This commit is contained in:
parent
2536e76617
commit
d1ce893633
12 changed files with 164 additions and 111 deletions
|
|
@ -1,5 +1,16 @@
|
|||
# State of Play
|
||||
|
||||
## 20260311
|
||||
|
||||
I've still been having trouble with runaway recursion — in `member`, but
|
||||
due to a primitive bug I haven't identified — so this morning I've tried
|
||||
to implement a stack limit feature. This has been a real fail at this stage.
|
||||
Many more tests are breaking.
|
||||
|
||||
However, I think having a configurable stack limit would be a good thing, so
|
||||
I'm not yet ready to abandon this feature. I need to work out why it's breaking
|
||||
things.
|
||||
|
||||
## 20260226
|
||||
|
||||
The bug in `member` turned out to be because when a symbol is read by the reader,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue