That suggestion made sense–I moved all my functions from my non-pollen.rkt 
modules into my root pollen.rkt, but it is still caching values until I 
restart the server and reset the cache. I opened up my repo in case you 
happen to have time to take a look; https://gitlab.com/bstro/richmond

If you `raco pollen start` and navigate to 
http://localhost:8080/body/hexagrams/3.html for instance, and then attempt 
to change the return value for the function ->monogram in ./pollen.rkt at 
line 204 (for instance, change (monogram (yang)) to (monogram "xxx"), and 
hit refresh, you should see the shape at the top of the page change. It 
won't, at least for me, until I halt the server and `raco pollen reset` the 
cache. 

On Friday, March 22, 2019 at 9:01:05 PM UTC-5, Matthew Butterick wrote:
>
>
> On Mar 22, 2019, at 6:06 PM, Brendan Stromberger <[email protected] 
> <javascript:>> wrote:
>
> It seems to still be caching, even with your code snippet, or even if 
> explicitly disabling the cache in each individual racket file. Also, 
> browser cache is off.
>
>
> I'm afraid it's hard for me to offer a better answer without a full 
> example that demonstrates the failure. Cache invalidation is one of the two 
> famously difficult problems in programming (the others being naming things, 
> and off-by-one errors). 
>
> For instance, if your "pollen.rkt" files import bindings from other .rkt 
> modules, those secondary modules will be cached. Would you believe there's 
> another setup value called `cache-watchlist` [1] that lets you specify 
> other files that the cache should notice.
>
>
> [1] 
> https://docs.racket-lang.org/pollen/Setup.html#%28def._%28%28lib._pollen%2Fsetup..rkt%29._setup~3acache-watchlist%29%29
>  
> <https://docs.racket-lang.org/pollen/Setup.html#(def._((lib._pollen/setup..rkt)._setup~3acache-watchlist))>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to