This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-26
Channels
- # aleph (2)
- # aws-lambda (18)
- # beginners (81)
- # boot (3)
- # cider (25)
- # cljs-dev (274)
- # cljsjs (10)
- # clojars (25)
- # clojure (65)
- # clojure-austin (1)
- # clojure-brasil (2)
- # clojure-dev (33)
- # clojure-dusseldorf (6)
- # clojure-gamedev (3)
- # clojure-italy (17)
- # clojure-poland (3)
- # clojure-russia (7)
- # clojure-spec (48)
- # clojure-uk (45)
- # clojured (1)
- # clojurescript (26)
- # core-logic (2)
- # data-science (4)
- # datascript (6)
- # datomic (58)
- # defnpodcast (2)
- # docker (1)
- # duct (14)
- # figwheel (2)
- # fulcro (130)
- # graphql (3)
- # leiningen (1)
- # liberator (15)
- # luminus (5)
- # nrepl (1)
- # numerical-computing (1)
- # off-topic (45)
- # onyx (15)
- # re-frame (9)
- # reagent (3)
- # ring (1)
- # shadow-cljs (91)
- # spacemacs (8)
- # sql (23)
- # unrepl (38)
- # videos (2)
- # vim (12)
is it intentional that clojure.core.cache/ttl-cache-factory returns an object with no ttl data attached to it? this seems absurd
I'm hoping I'm just using it wrong (binding [*print-meta* true] (prn (clj-cache/ttl-cache-factory {})))
=> {}
- where's the TTL?
(binding [*print-meta* true] (prn (clj-cache/ttl-cache-factory {} :ttl 30000)))
=> {}
@noisesmith Check the type -- it's a TTLCache
object.
@seancorfield: not in my repl
I’ve been looking for someone to help maintain core.cache btw. If you’re interested, let me know. :)
ideally someone actually using it for stuff
seancorfield: oh! so weird, I didn't expect that, you are correct
(type (cache/ttl-cache-factory {} :ttl 3000))
=> clojure.core.cache.TTLCache
yeah, I just verified - the way it printed didn't make it obvious (I'm used to records and such with reader tags clearly)
We use core.cache
pretty heavily so I could take it on I guess @alexmiller -- I don't expect it actually needs much "maintenance"?
iirc there are a few tickets out there that could probably use some attention
it has open issues in jira
I would be happy to have your help @seancorfield
19 open issues (and a still-open pull request)... fair enough...
And some pretty important ones open for three years... OK, sure. My wife's traveling a lot in March (China twice and Taiwan once, as well as an East Coast US trip) so I'll have plenty of alone time at weekends to work on it! Sign me up @alexmiller!
would it be worth making a patch for the cache types to have reader tags in their printed representation?
@noisesmith It would probably help folks trying to debug core.cache
-using code.
(I guess I'll have to roll my sleeves up and take a look this weekend!)
I may be an outlier but it would also help my code - I normally use a database as the storage backend (instead of an in-memory atom or whatever), and encode / revive via the transit library. By accident my code happens to work even when I lose the custom cache types, but it would have broken if the db itself didn't enforce a ttl by deleting records.
Feel free to open a JIRA issue outlining what you'd like to see 🙂
@seancorfield fair warning that core.memoize tends to be pretty tightly coupled to core.cache as a consumer and usage
Yup, and we use that heavily too.
Who is maintaining memoize these days?
no one :)
or rather, I look at it occasionally but don’t have time to really do anything good with it
would love to have someone handling that too :)
Well, they go together so sign me up 🙂
ok :) you won’t manage them any less than I am :)
Hah! An underwhelming vote of confidence! 🙂
oh, I’m confident you’ll do great. just saying that I have set the bar low for you. :)
I’ve switched over jira and the build box to make you owner. let me know if you need anything else (I think github is probably ok already?)
Thanks. Will ping you if I need anything else!