Fork me on GitHub
#cider
<
2019-04-30
>
qythium10:04:41

@jumar yeah, just wanted to make sure I wasn't missing anything obvious. I think it's quite a fundamental operation a user would try to do - "inspect this intermediate data structure in front of me that won't fit on the screen" and having to navigate around the buffer and yank things is a lot of unnecessary friction

qythium10:04:12

maybe I'll look into it on the weekend and see how to add that functionality

qythium10:04:18

ideally without having to re-evaluate the form, which may be side-effecting / expensive

bozhidar10:04:31

I’m not arguing about the usefulness of something like this and contributions would be appreciated. Unfortunately lately we’ve had little time for work on the debugger.

gfredericks18:04:06

does cider print arrays as vectors by default? mine is doing this and I can't remember if I've configured anything weird; I'd like to get it to stop doing that

dromar5618:04:40

By default cider uses clojure.pprint/pprint (you can check the variable cider-print-fn to see if you've changed it), which prints vectors as [1 2 3] and arrays as [1, 2, 3]

gfredericks18:04:34

@dromar56 thanks, that seems to explain it

gfredericks18:04:50

I probably used to override it and somehow stopped

gfredericks18:04:01

I definitely didn't know that pprint printed arrays like that

dromar5618:04:26

And I didn't knew the difference between arrays and vectors in clojure until 5 minutes ago 😛

gfredericks18:04:23

they're pretty different

dromar5618:04:00

Yes it was pretty interesting to read about them. Since I have 0 java background I haven't looked into java interop yet, and hadn't met them

gfredericks18:04:10

byte arrays are probably the most common to encounter, especially if you're dealing with anything big; they'll be at least eight times (or more??) more memory efficient than a naive "sequence of numbers" clojure approach