You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The thread by default created with current-thread-custodian, which will slow down the whole DrRacket, particular if I'm working on some large project (not really large in normal scale, but racket level large).
Now I'm thinking, if interval-map cannot cross the boundary, it seems forward every message to place is more reasonable now……Though that is a big refactoring.
dannypsnl
changed the title
refactoring plan about improve the respondability
refactoring plan about improve the respond ability
Sep 14, 2024
Is your feature request related to a problem? Please describe.
The thread by default created with current-thread-custodian, which will slow down the whole DrRacket, particular if I'm working on some large project (not really large in normal scale, but racket level large).
The fundamental problem is
sauron/collect/record-maintainer.rkt
Line 79 in fb2eaa9
collect-from
is computation intensive operation, move it into a place worker seems reasonable.Describe the solution you'd like
Describe alternatives you've considered
No idea
Additional context
I found
(place-message-allowed? (make-record))
is#f
, the reason are fields that involve(make-interval-map)
.The text was updated successfully, but these errors were encountered: